Hiram said the following in a recent post: "The STOMP spec does not
explicitly define a way to finely control the flow of messages of a
subscription but implementations are free add extensions to support that
functionality".
That leads me to question I have been wanting to ask for a while. Are
there any plans to introduce formal support for extensions to the STOMP
protocol? This could be done in a similar way to the way is done in the
WebSocket protocol, i.e. new "accept-extensions" header in the CONNECT
frame to request extensions, new "extensions" header in the CONNECTED
frame where the server states which of the requested extensions are active.
thanks,
Chris
Hiram Chirino
Software Fellow | FuseSource Corp.
chi...@fusesource.com | fusesource.com
skype: hiramchirino | twitter: @hiramchirino
blog: Hiram Chirino's Bit Mojo