[jira] Created: (STOMP-21) libstomp-c : too strict protocol implementation (\n requested at end of frame)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (STOMP-21) libstomp-c : too strict protocol implementation (\n requested at end of frame)

JIRA jira@codehaus.org
libstomp-c : too strict protocol implementation (\n requested at end of frame)
------------------------------------------------------------------------------

                 Key: STOMP-21
                 URL: http://jira.codehaus.org/browse/STOMP-21
             Project: Stomp
          Issue Type: Bug
         Environment: Linux CentOS 5.6
            Reporter: Louis GOUNOT
            Priority: Critical
         Attachments: stomp.c.patch

libstomp-c current implementation requires a '\n' to be sent from broker. This is however not required by protocol as described at <http://stomp.codehaus.org/Protocol>.
When a frame is received without a trailing '\n', a APR_EGENERAL is raised when following frame is sent by broker. Easily testable against RabbitMQ 2.4.1 with stomp plugin

I have joined a patch for "stomp.c" file in order to have an implementation more compliant to protocol.

Patch allows to have or not a '\n' at end of frames. It also allows any "spacing" characters between frames (using "isspace" function from <ctype.h>).

I have tested patched version against :
    - RabbitMQ 2.4.1 with stomp plugin
    - Dummy "nc -l" sending same frames as those from RabbitMQ but with '\' at end of frames

I would really appreciate this patch be fully integrated in official release as are starting a project which will require it.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email