search

benjaminws / stomp-js

Implementation of the STOMP protocol in node.js
BSD 3-Clause "New" or "Revised" License
87 stars 47 forks source link

Partial messages in ondata event being processed as completed #32

Open pedromarce opened 10 years ago

pedromarce commented 10 years ago

Hi,

I am a bit surprised that this is not working and I am wondering if it is me doing something wrong.

Problem is when receiving a large message (plain/text), information is processed and the Frame is created even if the message is not completed (the socket would have had received eventually all information as I have checked) but in the first data event is processed without contemplating the case of not being complete.

Is this some sort of configuration issue, or is it just not coded at the moment?

If it is the second case I would probably give it a go to try to fix it.

Regards,

keeneym commented 10 years ago

I am also having this issue. Have you found a fix for this?

pedromarce commented 10 years ago

No, sorry, I finally moved to stomp-client library that was working fine.

https://github.com/easternbloc/node-stomp-client

keeneym commented 10 years ago

Thanks for the quick response. I'll check it out.