Re: [alto] SSE final touches

[Jan Seedorf <[e-mail]>]

Hi Richard,

>
> 2. One next step we are considering is the support of multipart 
> update. The sever may send a multipart message consisting of multiple 
> objects say A, B, ... each of which is a top level JSON object.. Both 
> merge patch and JSON patch support only a single object and hence 
> cannot apply if we want incremental updates. Hence, if we want 
> incremental updates, we need to provide an individual client-id for 
> each part of a multipart content.

what is the motivation behind the multipart update? Sure it is a nice 
feature, but as you know, we are trying to finalise SSE asap. So we 
would only like to introduce new feature at this time if they are 
absolutely needed.

  - Jan


On 17.03.18 14:07, Y. Richard Yang wrote:
> Dear all,
>
> As we finalizing all aspects of SSE, two issues need some discussions. 
> Quick updates, without delaying the progress, can produce a higher 
> quality  document.
>
> 1. It is the notification-of-remove response issue. It is already 
> being started in an earlier thread. Any opinions will be appreciated.
>
>
> Another alternative design is that we require that each potential 
> multipart service also allow individual transmissions. This is the 
> write up in the current version. Any quick discussions will be great.
>
> See you in London.
> Richard
> -- 
> Richard
>
>
> _______________________________________________
> alto mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/alto