{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/automotive/issues/92","repository_url":"https://api.github.com/repos/w3c/automotive","labels_url":"https://api.github.com/repos/w3c/automotive/issues/92/labels{/name}","comments_url":"https://api.github.com/repos/w3c/automotive/issues/92/comments","events_url":"https://api.github.com/repos/w3c/automotive/issues/92/events","html_url":"https://github.com/w3c/automotive/pull/92","id":177901409,"number":92,"title":"applying some of meeting results","user":{"login":"wonsuk73","id":1696315,"avatar_url":"https://avatars.githubusercontent.com/u/1696315?v=3","gravatar_id":"","url":"https://api.github.com/users/wonsuk73","html_url":"https://github.com/wonsuk73","followers_url":"https://api.github.com/users/wonsuk73/followers","following_url":"https://api.github.com/users/wonsuk73/following{/other_user}","gists_url":"https://api.github.com/users/wonsuk73/gists{/gist_id}","starred_url":"https://api.github.com/users/wonsuk73/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wonsuk73/subscriptions","organizations_url":"https://api.github.com/users/wonsuk73/orgs","repos_url":"https://api.github.com/users/wonsuk73/repos","events_url":"https://api.github.com/users/wonsuk73/events{/privacy}","received_events_url":"https://api.github.com/users/wonsuk73/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-09-19T21:21:28Z","updated_at":"2016-09-21T00:25:08Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/w3c/automotive/pulls/92","html_url":"https://github.com/w3c/automotive/pull/92","diff_url":"https://github.com/w3c/automotive/pull/92.diff","patch_url":"https://github.com/w3c/automotive/pull/92.patch"},"body":"- made clear sentence for “The mechanisms will include WebSockets and REST”\n- removed “The APIs developed by this group may use a different security model from the traditional browser security model.” and “Hence, it is conceivable that it is used/implemented without using the Vehicle Signal Server Specification.”\n- fixed typos"},"comment":{"url":"https://api.github.com/repos/w3c/automotive/issues/comments/248475727","html_url":"https://github.com/w3c/automotive/pull/92#issuecomment-248475727","issue_url":"https://api.github.com/repos/w3c/automotive/issues/92","id":248475727,"user":{"login":"peterMelco","id":12607486,"avatar_url":"https://avatars.githubusercontent.com/u/12607486?v=3","gravatar_id":"","url":"https://api.github.com/users/peterMelco","html_url":"https://github.com/peterMelco","followers_url":"https://api.github.com/users/peterMelco/followers","following_url":"https://api.github.com/users/peterMelco/following{/other_user}","gists_url":"https://api.github.com/users/peterMelco/gists{/gist_id}","starred_url":"https://api.github.com/users/peterMelco/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/peterMelco/subscriptions","organizations_url":"https://api.github.com/users/peterMelco/orgs","repos_url":"https://api.github.com/users/peterMelco/repos","events_url":"https://api.github.com/users/peterMelco/events{/privacy}","received_events_url":"https://api.github.com/users/peterMelco/received_events","type":"User","site_admin":false},"created_at":"2016-09-21T00:25:07Z","updated_at":"2016-09-21T00:25:07Z","body":"Hi All!\n\nI also have a basic question that I think we answered in F2F in Portland - I have forgotten (as usual). The introduction of a request id is motivated by what ? Why is it not sufficient to use the session id to identify the request per session ? I think that Adam and Kevin had a good explanation for it ...\n\nBr\nPeter Winzell\n________________________________\nFrån: Shinjiro Urata [notifications@github.com]\nSkickat: den 20 september 2016 10:34\nTill: w3c/automotive\nÄmne: Re: [w3c/automotive] applying some of meeting results (#92)\n\n\nExcuse me for asking basic question.\nDo we need to keep REST mechanism?\n\n  *   In my understanding, RESTful API is http based mechanism which is good for one shot request such as get(), set() but not good for subscribe(). This is because, in subscribe(), server have to push data to client without client's request.\n  *   As personal opinion, most people would be satisfied with Websocket based server spec.\n  *   REST based spec will be considerably different from Websocket based spec. If websocket mechanism is enought, it might be redundant effort to create REST spec.\n\nI'd like to know if there is special reason that we should keep REST mechanism.\n\n—\nYou are receiving this because you are subscribed to this thread.\nReply to this email directly, view it on GitHub<https://github.com/w3c/automotive/pull/92#issuecomment-248238905>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMBf_vGMcj6BSRBzxT0E3VEblOLNk8lWks5qr5qLgaJpZM4KA-os>.\n"}}
{"actor":{"display_login":"peterMelco"}}