I think that is a wise decision. One can continue adding bits and pieces to the protocol ad infinitum. Best to get what we have out and let the implementations and needs then guide us towards whether multipart update will serve a substantive community. If it does, I suspect that willing hands will rise to scratch that particular itch.
>From my understanding, nothing is preventing the update of multiple objects, just that with the current constructs, they have to be done serially instead of in parallel. Cheers, On 03/18/2018 12:16 PM, 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! - vijay -- Vijay K. Gurbani / [email protected] Network Data Science, Nokia Networks Calendar: http://goo.gl/x3Ogq _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
