-
Notifications
You must be signed in to change notification settings - Fork 276
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
move recv() loop from uasc into opcua package #211
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First round.
@dwhutchison does this conflict with #207 ? If not, then we can merge this. |
One small optimization could be to create a |
In preparation for a server implmentation, move the main read loop out of the uasc package and allow the caller (client / server) to receive unsolicited uasc messages.
fd7c7f1
to
024329a
Compare
Force-push just to rebase to master |
This should be OK to merge; tests are passing and the examples are functional. |
Then lets merge it and move on. |
In preparation for a server implementation, move the main read
loop out of the uasc package into the application layer. The primary change is
recv()
(renamed toreceive
), now returns each time it receives a full message. This allows the caller (client or server) to receive unsolicited uasc messages from the channel.The context can be better seen in https://github.com/gopcua/opcua/tree/feature/server although that code isn't fleshed out enough to merge. The remainder of the server implementation shouldn't have further impact on the uasc package as this change so I'm hoping to get this into the main branch to avoid needing to constantly fix merge conflicts with master.