tyrus
  1. tyrus
  2. TYRUS-185

Composition of different frame/message processors

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.x-backlog
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            jitu
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: