I wrote: >> [image() on a connected socket will return] >> "file(:1234:192.168.1.69:45987)" representing a connection from >> the host 192.168.1.69, port 45987.
David Gamey <David.Gamey> writes: > Hmmm ... a small suggestion. How about separating the two sockets > differently eg. "::" or ";". I don't even want to think about > what will happen with IPv6 addressing! I modelled this on the syntax used by ssh for port forwarding. It's easy to handle with string scanning. I don't like the "::" idea because multi-char delimiters are a pain; ";" is ok but what does it gain over ":"? (Incidentally, if you grab the latest code from CVS, this has been implemented; you can try it out. Just don't use select() on pipes.) -s _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
