> That collection part is being taken care of by the client, and, since > they're writing the collector in C++, have a couple options > on how to give > me that data.
Evan, I can see why you might be concerned about overhead when using a data "pull" method rather than a data "push." However, with the data you are working with, it may be a nit you are picking. Director has always been strongest and most stable working at its own pace. Cramming data down its throat (I'm sure you had some sort of message queueing system in mind, but even still) isn't ideal. Why not just go with the simple solution of a central database? Have the C++ dll dump it's data into there with a timedate stamp, and have Director pull the data out every exitFrame. This way, both applications are working at a comfortable level. Even with lulls, Director's querying the DB should be a millisecond blip on the radar with no ill results. Just test your DB backend to make sure it can take constant querying. Brian Romanko Lead Developer - Neo/SCI Corporation Member - Greater Rochester Macromedia User Group [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
