2 Replies Latest reply on Feb 18, 2010 9:16 AM by timfox

    STOMP protocol status

    timfox

      What's the ETA for completion of STOMP protocol?

       

      As far as I can see, there remains:

       

      1) Fix FrameDecoder issue

      2) Optimise - current impl will be slow since it uses streams etc for decoding

      3) Anything else?

      4) Encoding issues - currently uses core types  + UTF encoding

       

      I'd like to get this task put to bed if possible, so we can move on to something else...

        • 1. Re: STOMP protocol status
          jmesnil

          Fixing and optimizing the frame decoder should take 2 days. I also notice that the tests ran significantely faster on netty 3.2.0.ALPHA.

          I have no other pending tasks planned for this integration.

           

          About the encoding issues, could you reply on the previous dev post so we agree on what needs to be done?

          • 2. Re: STOMP protocol status
            timfox
            Not sure what thread you mean...