Hi Wendy,

Thank you so much for the reply! I reviewed the draft together with Mingming 
and I think your answer solved our confusion. And the revision also looks great.

By the way, there is a typo in the draft. In the first line of chapter 6.1 ALTO 
Event Format, "basic stucture” should be “basic structure”.

Best,
Yichen


> On Jul 9, 2016, at 1:36 AM, Wendy Roome <[email protected]> 
> wrote:
> 
> Mingming,
> 
> Thanks for reading it!
> 
> (1) The paragraph is somewhat confusing.  I will replace the last two 
> sentences with something like
> 
> The control URI allows a client to modify the newly-created update stream. 
> For example, by sending requests on the control URI, the client can request 
> the server to send update events for additional resources, to stop sending 
> updates for previously requested resources, or to gracefully stop and close 
> the update stream altogether.
> 
> p24: I will add an example of using the control uri to add a resource as well 
> as remove one.
> 
> (2) "Two new lines" means two line-separators in a row, where a 
> line-separator is a new-line, carriage-return, or carriage-return/new-line. 
> (*Sigh* I wish the IETF could standardize line endings!!)
> 
> I will re-phrase that is to say that an event is terminated by a blank line 
> (no fields).
> 
>       - Wendy
> 
> From: Mingming Chen <[email protected] <mailto:[email protected]>>
> Date: Thu, July 7, 2016 at 11:21
> To: Wendy Roome <[email protected] <mailto:[email protected]>>
> Cc: IETF ALTO <[email protected] <mailto:[email protected]>>
> Subject: SSE review
> 
> Hi Wendy,
> Yichen and I are reviewing SSE, here are something uncertain for us and we 
> want to discuss.
> (1) In 2. Overview of Approach part, page 6, " The server responds by sending 
> an event with the URI of a stream-control resource for this update stream. 
> The client uses the control URI to select the resources for which it wants 
> updates". We are not sure what's the meaning of " The client uses the control 
> URI to select the resources for which it wants updates". Do you mean the 
> "add" control ( location 3. Changes Since Version -01,page 6, "Defined a new 
> 'Stream Control' resource to allow clients to add or remove resources from a 
> previously created Update Stream")? 
> In 9.2 Example: Advanced Network and Cost Map Updates, page 24, there is a 
> good example of updates. But we didn't find an example of clients using the 
> stream control URI to execute "add" control but just "remove". 
> (2) In 4. Overview of Server-Sent Events (SSEs), page 7, "Messages are 
> delimited by two new-lines (this is a slight simplification: see [SSE] for 
> details)." But in the following, "The protocol defines three field names: 
> event, id, and data". The example in Figure 1 also illustrate the three field 
> names. So the question is, what is the "two new-lines" refer to?
> Look forward to your reply! Thank you so much!
> 
> 
> Best Regards,
> Mingming, Yichen
> _______________________________________________
> alto mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/alto

_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to