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

Ensure thread safety #4

Open
amorphic opened this issue Sep 25, 2014 · 0 comments
Open

Ensure thread safety #4

amorphic opened this issue Sep 25, 2014 · 0 comments
Labels

Comments

@amorphic
Copy link
Owner

If thread A and thread B both send commands to a tosr0x device in quick succession it it currently possible for thread A to receive thread B's response and vice versa.

Currently there is thread locking in place which attempts to isolate each thread's communication with the device. But apparently this isn't working in all cases.

A good suggestion in this post suggests using a queuing mechanism:

http://stackoverflow.com/questions/4043193/python-how-to-share-a-serial-port-with-two-different-threads-class-a-class-b

@amorphic amorphic added the bug label Sep 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant