Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[tcpros -subscriber ] receiving a big message failed du to tcp window #33

Open
maxired opened this issue Jul 12, 2012 · 2 comments
Open

Comments

@maxired
Copy link
Contributor

maxired commented Jul 12, 2012

Being a subscriber receiving a big mesage, ie a sensor_msgs/image with a big image, receiving the message failed.

The fact is that we try to parse the message but we have only a part of the message.
We got only part of the message because du to the TCP behavior, the ros message is splitted in different tcp packets.

We need to bufferized the packet until the size of the received data is equal to the length of the message.

@baalexander
Copy link
Owner

Oh, interesting. I agree the packets need buffered then. Do you know if the TCP library emits an event when the payload has finished?

@maxired
Copy link
Contributor Author

maxired commented Jul 12, 2012

The fact is it's not TCP jobs. This is an "application" issue, and that's why the length is the first thing to be transmitted in the ROS message protocol.

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

No branches or pull requests

2 participants