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

Handle receiving a magic start sequence in two separate parts #12

Merged
merged 1 commit into from
Aug 14, 2015

Conversation

varzac
Copy link
Contributor

@varzac varzac commented Aug 14, 2015

Previously if the StreamProtocolHandler was fed bytes that contained only
part of the Magic field that specifies the start of a message it would
throw away that start as it couldn't find the whole field. Now, it is
aware of that possibility and keeps enough bytes around that it won't miss
a Magic field.

Signed-off-by: Zach Varberg Zachary.Varberg@Digi.com

Previously if the StreamProtocolHandler was fed bytes that contained only
part of the Magic field that specifies the start of a message it would
throw away that start as it couldn't find the whole field.  Now, it is
aware of that possibility and keeps enough bytes around that it won't miss
a Magic field.

Signed-off-by: Zach Varberg <Zachary.Varberg@Digi.com>
@posborne
Copy link
Contributor

Tests on Travis failed at first but it was just a problem pulling from pypi, so I restarted.

@posborne posborne merged commit 1ed87bb into master Aug 14, 2015
@posborne posborne deleted the parsing-start-field branch August 14, 2015 16:08
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

Successfully merging this pull request may close these issues.

None yet

2 participants