That is a great idea. If you do that, I have an improvement to Net::Stomp would like to submit. The improvement I made include: I have implemented the Stomp protocol spec that dealing with "content-length" header field. This is need to support JMS Bytes Message since the presence of content-length may be used to indicate binary data.
The SEND frame can incude content-length header with the message body length. I have modified the code to handle the frame reading by spliting command/header from the body. It first reads the header and check to see if content-length is specified. If so, reads content-length bytes plus terminating null byte and process it binary data. If content-length is not specified, reads the body of the message until it runs into the first null byte. I have tested it with the following combinations successfully: 1. Perl-to-Perl Stomp clients Text Messages. 2. Perl-to-Perl Stomp clients Bytes Messages. 3. PerlStomp-to-Java MS clients Text Message 4. JavaJMS-toPerlStomp clients Text Message 5. PerlStomp-to-JavaJMS clients Bytes Message Failed to send Bytes Message from JavaJMS to PerlStomp: 6. JavaJms-to-PerlStomp clients Bytes Message I do believe this last case is due to Java JMS/Stomp server not writing to the client socket. Either I read zero byte or 1 byte which is newline. The Stomp server team help in this regard is appreciated. Please let me know, I will put the patch to Net::Stomp and Leon can review it. Thanks in advance, Sileshi James.Strachan wrote: > > BTW we could maybe reuse codehaus's JIRA to track bugs for Net::Stomp > if you like? > > On 10/20/06, sileshi <[EMAIL PROTECTED]> wrote: >> >> Leon, it is great you wrote theNet::Stomp module. The best Stomp >> implementation >> compared the other two I have worked with before. I have used the >> Net::Stomp >> module with great success. I highly recommend. >> The problem I run into are in the area that involves JMS BytesMessage >> being >> sent to destination a Perl Stomp client consumes. I look like JMS >> BytesMessage >> is not passed to Stomp Server. I will make a separate entry on this >> issue. >> >> My question for you is how do I file bug in case if I run into one? >> >> Thanks in advance. >> -Sileshi >> >> >> >> Leon Brocard wrote: >> > >> > Hello all, >> > >> > Just a heads up to say that I've written a Stomp client for Perl. It >> > works well for my uses and is fairly well documented but I haven't >> > really tested interoperability (as I can see from AMQ-978). >> > It's available from the CPAN and I welcome your ideas on improving it: >> > >> > http://search.cpan.org/dist/Net-Stomp/ >> > >> > Cheers, Leon >> > >> > ps thanks for activemq! >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Stomp-in-Perl%3A-Net%3A%3AStomp-tf2478545.html#a6925493 >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Stomp-in-Perl%3A-Net%3A%3AStomp-tf2478545.html#a6943843 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
