Re: IAC (native port listening not possible):howaboutexternals/named pipes?

2004-04-24 Thread Dar Scott
On Saturday, April 24, 2004, at 04:06 AM, David Bovill wrote: Not as elegant (or fast I would think), as having the equivalent to accept with a message being sent when something comes in? Unfortunately, only socket I/O has message callback I/O. Sounds like open driver / file, would be a good ca

Re: IAC (native port listening not possible):howaboutexternals/named pipes?

2004-04-24 Thread David Bovill
Dar Scott wrote: On Friday, April 23, 2004, at 09:17 AM, David Bovill wrote: Thanks again. Read it - nice and clear. So I guess you could just write a daemon that continually checks for input using either open file or open driver for read. Try open file first. You might want to try a quick te

Re: IAC (native port listening not possible): howaboutexternals/named pipes?

2004-04-23 Thread Dar Scott
On Friday, April 23, 2004, at 09:17 AM, David Bovill wrote: Thanks again. Read it - nice and clear. So I guess you could just write a daemon that continually checks for input using either open file or open driver for read. Try open file first. You might want to try a quick test with a named p

Re: IAC (native port listening not possible): howaboutexternals/named pipes?

2004-04-23 Thread David Bovill
[EMAIL PROTECTED] wrote: Assuming your dedicated server is Linux, there is firewalling protection built into recent kernels - it is just a question of finding a good tool to control it. Thanks - so in your opinion would be OK to do this in a production / enterprise level server? Scares me - an