RE: [Flightgear-devel] Re: UDP port into the property tree
From: Melchior FRANZ [EMAIL PROTECTED] * dene maxwell -- Friday 17 February 2006 05:53: What port number for write ? What port number for read? (I prefer confirming protocols) That's called TCP, then. Yes, that's possible. Just run fgfs with --telnet=5500, then you can telnet into it and read/write to properties. $ fgfs --telnet=5500 Then wait until it's running, and from another terminal window telnet into it: $ telnet localhost 5500 help Valid commands are: cd dir cd to a directory, '..' to move back data switch to raw data mode dump dump current state (in xml) get var show the value of a parameter help show this help message ls [dir] list directory prompt switch to interactive mode (default) pwddisplay your current path quit terminate connection run command run built in command set var valset var to a new val show var synonym for get And the whole telnet/socket connection can also be done by a script. Look into scripts/ dir for examples. What format to access each property? Start withdata Then read... get /position/longitude-deg get /position/latitude-deg Or write ... set /sim/foo 123 and finally quit This way you can do about everything. Read/write properties, execute built-in commands, or transfer arbitrary Nasal code and let fgfs execute it. You can even transfer whole dialogs and pop them up in fgfs. m. That would suit my needs exactly if; a) I wanted to do it manually b) I could start a telnet session from within VB6 (not saying you can't just I haven't yet) was really hoping that it could be treated like an object using UDP. eg set com1.freq=129.6 set nav1.pri.freq=103.3 set nav1.sec.freq=105.3 set nav1.radial=161 set adf.freq=234 will have to investigate starting a telnet session within VB if no other ideas come to pass Cheers, thanks for the suggestion =Dene _ Shop til you drop at XtraMSN Shopping http://shopping.xtramsn.co.nz/home/ --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: UDP port into the property tree
From: Melchior FRANZ [EMAIL PROTECTED] * dene maxwell -- Friday 17 February 2006 10:18: That would suit my needs exactly if; a) I wanted to do it manually b) I could start a telnet session from within VB6 (not saying you can't just I haven't yet) Forget about telnet. It's a normal tcp socket connection. I'm confident that VB6 can do that. Did you look at the examples as I told you? The c/c++ examples in scripts/example/ don't even mention telnet. m. That was the second part of my question, what would the syntax be under UDP... the same? I understood Telenet was indeed a TCP connection (ie one to one) whereas UPD is unsigned and is (at least in the VB control) different to a TCP connection in that theoretically it could be many to one. but i'm skating on thin ice here so be gentle with me ;-) =Dene _ Looking for love? Check out XtraMSN Personals http://xtramsn.match.com/match/mt.cfm?pg=channeltcid=200731 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: UDP port into the property tree
From: Melchior FRANZ [EMAIL PROTECTED] * dene maxwell -- Friday 17 February 2006 10:18: That would suit my needs exactly if; a) I wanted to do it manually b) I could start a telnet session from within VB6 (not saying you can't just I haven't yet) Forget about telnet. It's a normal tcp socket connection. I'm confident that VB6 can do that. Did you look at the examples as I told you? The c/c++ examples in scripts/example/ don't even mention telnet. m. Melchoir, just looked up MSDN, I quote; Using the Winsock Control A WinSock control allows you to connect to a remote machine and exchange data using either the User Datagram Protocol (UDP) or the Transmission Control Protocol (TCP). Both protocols can be used to create client and server applications. Like the Timer control, the WinSock control doesn't have a visible interface at run time. Possible Uses Create a client application that collects user information before sending it to a central server. Create a server application that functions as a central collection point for data from several users. Create a chat application. Selecting a Protocol When using the WinSock control, the first consideration is whether to use the TCP or the UDP protocol. The major difference between the two lies in their connection state: The TCP protocol control is a connection-based protocol, and is analogous to a telephone the user must establish a connection before proceeding. The UDP protocol is a connectionless protocol, and the transaction between two computers is like passing a note: a message is sent from one computer to another, but there is no explicit connection between the two. Additionally, the maximum data size of individual sends is determined by the network. The nature of the application you are creating will generally determine which protocol you select. Here are a few questions that may help you select the appropriate protocol: Will the application require acknowledgment from the server or client when data is sent or received? If so, the TCP protocol requires an explicit connection before sending or receiving data. Will the data be extremely large (such as image or sound files)? Once a connection has been made, the TCP protocol maintains the connection and ensures the integrity of the data. This connection, however, uses more computing resources, making it more expensive. Will the data be sent intermittently, or in one session? For example, if you are creating an application that notifies specific computers when certain tasks have completed, the UDP protocol may be more appropriate. The UDP protocol is also more suited for sending small amounts of data. Regards =Dene _ Need more speed? Get Xtra Broadband @ http://jetstream.xtra.co.nz/chm/0,,202853-1000,00.html --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: UDP port into the property tree
From: Melchior FRANZ [EMAIL PROTECTED] * dene maxwell -- Friday 17 February 2006 10:50: From: Melchior FRANZ [EMAIL PROTECTED] Forget about telnet. It's a normal tcp socket connection. That was the second part of my question, what would the syntax be under UDP... the same? It would probably be the same. If it were implemented. But as it doesn't make the least sense, it isn't. m. Doesn't make the least sense sorry don't understand this ... Telenet being a application layer protocol requires alot more details as to recipient and also alot higher overhead to implement...whereas UDP being a trasport layer protocol is less distinct in is destination and requires less overhead to implement. Obviously interfacing at the different layers requires different levels of distinction regardsing destnation etc this would imply a different syntax at the very least. Cheers =Dene _ Read the latest Hollywood gossip @ http://xtramsn.co.nz/entertainment --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: UDP port into the property tree
Hi Melchior, I will read the documentation you suggest, thewy undoubtibly relay to FGv099 and I'm running FGv098a but I might be able to get enough out of them to make a start.. cheers =Dene From: Melchior FRANZ [EMAIL PROTECTED] Reply-To: flightgear-devel@lists.sourceforge.net To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Re: UDP port into the property tree Date: Fri, 17 Feb 2006 11:04:02 +0100 * Melchior FRANZ -- Friday 17 February 2006 10:57: * dene maxwell -- Friday 17 February 2006 10:50: That was the second part of my question, what would the syntax be under UDP... the same? It would probably be the same. If it were implemented. But as it doesn't make the least sense, it isn't. You probably want to read README.protocol, README.IO, README.multiplayer. m. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel _ Discover fun and games at @ http://xtramsn.co.nz/kids --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: UDP port into the property tree
dene maxwell wrote: Doesn't make the least sense sorry don't understand this ... Telenet being a application layer protocol requires alot more details as to recipient and also alot higher overhead to implement...whereas UDP being a trasport layer protocol is less distinct in is destination and requires less overhead to implement. This is basically wrong. TCP sockets are easier to implement for almost all applications, precicely because they are reliable. UDP will only look easier if you plan on skipping the code to recover from a lost packet. Some applications can do this, but the property tree can't -- property access is non-idempotent in the general case. Listeners can have side effects. I'm not sure what you mean about less distinct in destination, both TCP connections and UDP packets must go to a specific destination address (although you can use UDP to a broadcast address on your local LAN). Andy --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: UDP port into the property tree
Hi, ... Telenet being a application layer protocol requires alot more details as to recipient and also alot higher overhead to implement...whereas UDP being a trasport layer protocol is less distinct in is destination and requires less overhead to implement. I'm not sure what you mean about less distinct in destination, both TCP connections and UDP packets must go to a specific destination address (although you can use UDP to a broadcast address on your local LAN). Andy Exactly, TCP is point to point and UDP can be used for broadcast. The winsock control can do TCP or UDP with equal ease. Although I've only had experience using UDP because it's all I've ever needed to use (as per MSDN's recommendation that TCP be used for transferring large amounts of data and UDP for simple messaging type uses). The issue is the command structure that surrounds setting values in the property-tree... This is obviously written to cater for manual Telnet sessions. I was asking if there is access to the lower level that by-passes the need to use the command-structure (opening a session closing a session plus the other commands that were in there) and be able to treat the property-tree purely as an object that set or get type instructions can be issued to. Not that it is difficult to emulate the command-structure using either TCP or UDP. was just asking though. Cheers =Dene _ Looking for love? Check out XtraMSN Personals http://xtramsn.match.com/match/mt.cfm?pg=channeltcid=200731 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
