David, On localhost you can choose a random unused port and then write the port number to a file in a pre-defined place, all clients launching read from that file to learn which port to use. On lan, you can do like this, on the server part, when you accept connection do some handshaking, on the client part, just open the TCP connection and wait for the handshake, if it doesn't happen then you're talking to the wrong software, disconnect. You can also broadcast with datagrams, anyone using datagrams should have some sort of error control to prevent datagrams from wrong apps (also keep aware that datagram sizes varies with OS)
Andre On Sun, Jan 16, 2011 at 6:10 PM, Mark Wieder <mwie...@ahsoftware.net> wrote: > Jan- > > Sunday, January 16, 2011, 11:28:49 AM, you wrote: > > > Well, I figured I had better do it right away, so here it is: > > < > http://quartam.blogspot.com/2011/01/zeroconfbonjour-in-livecode-with-jmdns.html > > > > Awesome! Thanks. Bookmarked... > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
