Re: [alto] Issue about incr-updates-sse update stream control design

Thanks a lot for the points, Dawn. Please see below. On Sat, Mar 3, 2018 at 7:57 AM, Dawn Chan wrote: > Hi Jensen and Richard, > > Here are some of my ideas about the problem. > > Actually, the solution for option 1 is already mentioned in Section 8.6 of > the draft: > “If a request is successf

Re: [alto] Issue about incr-updates-sse update stream control design

Hi Jensen, Good question! Let's see the design space: 1. Client can send "add" or "remove"; since HTTP requests are "one-way", this needs to use a new control channel--a new HTTP request 2. Response option 1: Server notifies client outcome in the HTTP response by using a HTTP response code; 3. R

[alto] Issue about incr-updates-sse update stream control design

Hi incr-update-sse authors and all, I have a question about the current update stream control design in incr-updates-sse. In the last paragraph of Section 7.6.2, the document writes "When the client uses the stream control service to stop updates for one or more resources (Section 8