Re: [Jmap] Fwd: New Version Notification for draft-murchison-jmap-websocket-00.txt

[Ken Murchison <[e-mail]>]

On 05/29/2018 10:53 PM, Neil Jenkins wrote:
> Looks good.. A few thoughts:
>
>   * This should definitely be advertised in the capabilities object,
>     as per any JMAP extensions.
>

OK.  For now, I'll put the extension in the cyrusimap.org namespace.


>   * Should the server be allowed to advertise a different URL for a
>     websockets API connection as opposed to an HTTP one?
>

Sure.  I'll add a 'wsUrl' String to the capabilities.


>   * Are responses guaranteed to be in the same order as requests?
>     (Probably not; if you want methods to execute sequentially you
>     should bundle them in a single request object, but then how do you
>     correlate the response objects to the request objects? Probably
>     need to add an id property to the request/response object.)
>

I had intended that they would be in the same order, but I suppose out 
of order could be allowed if deemed necessary.


>   * I think being able to receive push events over the single
>     websocket connection makes sense, but that means you'd have to be
>     able to distinguish the different message types you might receive
>     (API response or push).
>

Can't the client distinguish between a Response object and a StateChange 
object?  If we need a better way, do you have a recommendation?


>   * What changes are required to rate limiting options for the server?
>     These probably need to be advertised in the capabilities object
>     for this extension.
>

Are you thinking that we need separate maxSizeRequest, 
maxConcurrentRequests, maxCallsInRequest, maxObjectsInGet, and 
maxObjectsInSet for the WebSocket connection?

-- 
Ken Murchison
Cyrus Development Team
FastMail US LLC