Here is some additional info that was requested: Message size is small (< 20 bits probably no more than 5 -- just enough to turn stuff on and off), but with at least 5 updates per second. At this point, I'm only envisioning streaming data. Reliability is not critical (i,e., system can tolerate message loss), however system cannot tolerate inaccurate messages, as we don't want to turn off/on something incorrectly, but if there is a short delay, that is acceptable. The solution has to be manageable by me which means that the software can't be wrapped up in highly complex networking algorithms that would be inaccessible by an 'engineer'. I need to at least manage changes in data (not necessarily data type, but at least what data is sent), and I need to be able to access the data in each beagle with either Python, C#, or some other simple language.
-- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/937bbabf-3972-4f7f-a8a4-0d1d997d0970%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
