Bug #826
Store commands in a queue
| Status: | Rejected | Start date: | 2012-05-18 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Mike Wozniewski |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | 0.6 | |||
| Version: |
Description
Generally, spin nodes should store an asynchronous queue of commands to be applied. Newer commands regarding the same attribute should override older ones. That way, SPIN won't slow down when a lot of messages are sent to it. (to change node attributes)
History
Updated by Mike Wozniewski 8 months ago
- Status changed from New to Rejected
This type of event compression is too hard to implement with SPIN's current "brute-force" OSC parsing. The only place that messages queue up is in the system's network buffers. We would have to implement another queue, which means that a new messaging system would need to be developed. Specifically, we would need to be able to identify which events can be compressed and which can't. For example, "setTranslation" could be compressed (ie, we only take the most recent), but "translate" cannot because each one needs to accumulate.