libstomp-c : too strict protocol implementation (\n requested at end of frame)

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.