Hi Ed, In support.
Christoffer On 27/05/2019 10:58, Edward Shryane via db-wg wrote: > (2) Implement a replacement NRTM interface > > The current NRTM is a custom protocol, which is complicated to use, and not > easy to extend without breaking existing clients. > > Instead implement a replacement NRTM interface, based on modern standards. > > - The interface is generally available without needing to be a member, or to > sign an agreement. > - The protocol uses HTTPS and WebSockets, with object data in JSON format. > - A client can request the current available range of updates, and also > request a closed or open range of updates. > - A separator comment is inserted between updates, with an 'end of stream' > comment after each group of updates. > - All object updates are returned, except for person and role objects. > - Personal data is filtered from all object updates, consistent with the > other query interfaces. > - A client can optionally request filtering updates by object type. > - A client can optionally identify themselves by providing credentials. > - The interface can be extended later by adding more request parameters.
signature.asc
Description: OpenPGP digital signature
