Hi Richard,
great, thanks, as chair I support that decision in the light of
finishing some charter items soon.
- Jan
On 18.03.18 18:16, Y. Richard Yang wrote:
Jan,
The authors had a very extensive discussion again. We have decided to
support only single-object ALTO resources, and leave multipart, which
can be a nice feature to support composition without the need of
accumulating all objects into a single object, as future work. We
edited a few sentences to make clear.
Thanks a lot for the guidance!
Richard
On Sun, Mar 18, 2018 at 5:55 AM, Jan Seedorf <[email protected]
<mailto:[email protected]>> wrote:
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
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/alto
<https://www.ietf.org/mailman/listinfo/alto>
_______________________________________________
alto mailing list
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/alto
<https://www.ietf.org/mailman/listinfo/alto>
--
--
=====================================
| Y. Richard Yang <[email protected] <mailto:[email protected]>> |
| Professor of Computer Science |
| http://www.cs.yale.edu/~yry/ <http://www.cs.yale.edu/%7Eyry/> |
=====================================
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
