Composition of different frame/message processors

We need composition of frame/message processors in Tyrus. That way, one can set up a pipeline based on the requirements. For simple endpoints, one could gather different frame/message processor requirements from endpoint method types and HTTP headers in the handshake. I could think of different pipelines for execution,

for e.g: A pipeline could be constructed using combination of the following processors for input messages.

Frame parser – (per-message | per-frame) extesion * - subprotocol handler * - Decoder Processor - Invoker

We can set up optimized pipeline based on the requirements and per connection.