Re: Re: Daemon - Child - Client - Server

[PyroX]

The web client may check back at any time between 5 seconds and 20 minutes, grab the que or buffered messages or actions and process them.

The child needs to maintain the connection to the 3rd party server at all times until the web client hangs up.

Initially we are talking about maybe 5 - 10 clients maximum. Later I would like to expand that to 25 or so.

Named Pipes, I will be looking into the possibility of using that. I guesd files would be acceptable as well, the child could just amintain a file with the buffer and the web client can work with the file, this of course adds another component to the equation, but maybe less complexity.

The 3rd party server is not very close, not local lan, not wan, but external to the network all-together. A timeout will not really be needed after connection, the child could notify the web client of the last buffer refresh and/or wether or not a update is needed. The only timeout here would be if the initial connection fails, or is lost later. Long periods of no data from the child is a possibility of course.

I had looked at some postings here on perl web server daemons that fork to a child, and will probably start with that.

Thanks for your help so far, everyone. All good info.