Re: [Flightgear-devel] Using Nasal to create a protocol
> "Ivan" == Ivan Ngeow writes: >> 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? Ivan> An alternate way is to purely use the --telnet protocol for Ivan> bidirectional communication. This means you have to poll FG to Ivan> find out how many AI aircraft there are, what their positions Ivan> are etc. There is no 'listener' interface with the telnet Ivan> protocol. Ivan> Using nasal to take advantage of the 'listener' interface and Ivan> crafting your own intelligent IPC property node is my Ivan> preferred route. I would agree. I would prefer a UDP-based protocol, so that I don't have to worry about dealing with discovering if FlightGear is running, and with dropped connections when FlightGear exits. I'll try out your Nasal suggestion and see how it works. Thanks! 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
Re: [Flightgear-devel] Using Nasal to create a protocol
Hi Brian. 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? > An alternate way is to purely use the --telnet protocol for bidirectional communication. This means you have to poll FG to find out how many AI aircraft there are, what their positions are etc. There is no 'listener' interface with the telnet protocol. Using nasal to take advantage of the 'listener' interface and crafting your own intelligent IPC property node is my preferred route. -ivan -- 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
Re: [Flightgear-devel] Using Nasal to create a protocol
> "Ivan" == Ivan Ngeow writes: Ivan> On 15/04/2010, Brian Schack 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
Re: [Flightgear-devel] Using Nasal to create a protocol
On 15/04/2010, Brian Schack 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? Getting back to the --generic protocol, you could manipulate the contents of a property node using Nasal and make FG dump the contents of that property via a TCP or UDP port. The reverse direction can be managed using the --telnet protocol. -ivan -- 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
Re: [Flightgear-devel] Using Nasal to create a protocol
> "Ron" == Ron Jensen writes: Ron> On Wednesday 14 April 2010 00:24:41 Erik Hofman wrote: >> Brian Schack wrote: >>> Is it possible to use Nasal to create a new FlightGear protocol? >>> None of the existing protocols (including generic) will do what >>> I need. >> >> I don't think so but I'm not a Nasal expert. I'm not even sure if >> I would like Nasal top be able to do so but that's for another >> discussion. Ron> It does sound like it would open a gaping security hole to Ron> allow nasal to directly communicate with the outside world. Ron> However nasal can write to files in directories explicitly Ron> allowed in $FG_ROOT/Nasal/IORules so perhaps, if you are on Ron> Linux, some creative use of pipes could help. 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? 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
Re: [Flightgear-devel] Using Nasal to create a protocol
On Wednesday 14 April 2010 00:24:41 Erik Hofman wrote: > Brian Schack wrote: > > I posted this question a few days ago, but got no response, so here we > > go again ... > > > > Is it possible to use Nasal to create a new FlightGear protocol? None > > of the existing protocols (including generic) will do what I need. > > I don't think so but I'm not a Nasal expert. I'm not even sure if I > would like Nasal top be able to do so but that's for another discussion. > > Erik > It does sound like it would open a gaping security hole to allow nasal to directly communicate with the outside world. However nasal can write to files in directories explicitly allowed in $FG_ROOT/Nasal/IORules so perhaps, if you are on Linux, some creative use of pipes could help. Ron -- 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
Re: [Flightgear-devel] Using Nasal to create a protocol
Brian Schack wrote: > I posted this question a few days ago, but got no response, so here we > go again ... > > Is it possible to use Nasal to create a new FlightGear protocol? None > of the existing protocols (including generic) will do what I need. I don't think so but I'm not a Nasal expert. I'm not even sure if I would like Nasal top be able to do so but that's for another discussion. Erik -- 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
[Flightgear-devel] Using Nasal to create a protocol
I posted this question a few days ago, but got no response, so here we go again ... Is it possible to use Nasal to create a new FlightGear protocol? None of the existing protocols (including generic) will do what I need. Thanks, 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
