Skip to content
This repository has been archived by the owner on Nov 28, 2018. It is now read-only.

Partial messages in ondata event being processed as completed #32

Open
pedromarce opened this issue Dec 9, 2013 · 3 comments
Open

Partial messages in ondata event being processed as completed #32

pedromarce opened this issue Dec 9, 2013 · 3 comments

Comments

@pedromarce
Copy link

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
Copy link

keeneym commented Jul 2, 2014

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

@pedromarce
Copy link
Author

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

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

@keeneym
Copy link

keeneym commented Jul 3, 2014

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants