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

buffer for proto/osc.c incoming messages #5

Closed
wrl opened this issue Jun 23, 2010 · 1 comment
Closed

buffer for proto/osc.c incoming messages #5

wrl opened this issue Jun 23, 2010 · 1 comment

Comments

@wrl
Copy link
Member

wrl commented Jun 23, 2010

currently, there is only a facility for buffering one incoming /press message...in the case of an asynchronous application in which monome_next_event() is called rarely, there is an overwhelming chance that events will be missed.

propose implementing a basic ringbuffer.

@wrl
Copy link
Member Author

wrl commented Jun 24, 2010

but wait! since we only call lo_server_recv_noblock() once per monome_next_event(), it should be okay. the liblo documentation suggests that only one message is dispatched per call to said recv function.

This issue was closed.
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

1 participant