>>>>> "Ivan" == Ivan Ngeow writes: Ivan> On 15/04/2010, Brian Schack <bschack-flightg...@usa.net> wrote: >>>>>>> "Ron" == Ron Jensen writes: >> >> Thanks for the reply. Unfortunately I need a general solution, >> one that works on Windows as well. >> >> Just to confirm: Nasal at the moment offers no interprocess >> communications abilities?
Ivan> Getting back to the --generic protocol, you could manipulate Ivan> the contents of a property node using Nasal and make FG dump Ivan> the contents of that property via a TCP or UDP port. The Ivan> reverse direction can be managed using the --telnet protocol. That's an interesting idea. I'll tell you what I'd like, and we'll see if those of you who know more about this than I do (ie, nearly everyone :-)) can help. What I want to do is have Atlas monitor the state of all AI aircraft. The number of AI aircraft varies, so that's why I didn't think the generic protocol would work - the generic protocol only allows you to specify a fixed number of properties to transmit. So, would it be possible to use Nasal to package all the data (into a string say), plop it into a property node, and then use the generic protocol to send that node? Is there an even better way? Brian ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel