IAC (native port listening not possible): howaboutexternals/named pipes?
david at opn-technologies.com
Fri Apr 23 10:17:26 CDT 2004
revolution at knowledgeworks.plus.com 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 - and I'm not even paranoid :)
>There is also an article here
>on using named pipes in Linux. If you want to go down that route, maybe
>you can achieve it more quickly than porting the project you mentioned (as
>interesting as that project sounds).
>Hope this is of some help.
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. Not as elegant (or fast I would think), as having
the equivalent to accept with a message being sent when something comes
in? I guess this is what writing a small external would do - wrap the C
"receiver code" in the external API stuff... and hopefully be able to
define / send a message when something comes in?
More information about the use-livecode