On Dec 9, 2011 8:56 AM, "Brian Lloyd" <[email protected]> wrote: > In the case of running where both the TNC and the KISS client are inside the same machine, I would expect to find a virtual serial port program connecting the two. OTOH, in unix I would probably use a named pipe. I would NOT use a socket in the networking stack. It makes no sense to me.
I don't see why a pipe or a virtual rs232 driver is OK but a TCP connection isn't. At this point any such abstraction is the same...just a reliable way to send data bidirectionally. The BSD socket abstraction makes TCP connections and named pipes look the same anyway. Overhead difference on the same machine is trivial and possibly the lo interface gets more attention from developers anyway because X is written to use TCP, not pipes. There is a trend these days to small devices (wrt54g, arduino, quisk on fpga) communicating via IP. Leigh/WA5ZNU
_______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
