Re: IPC Confusion

[bennymack]

Of course, as with all things Perl, there is more than one way to do it.

I guess I'd like to answer your question with a question in typical XY fasion. What are you ultimately trying to accomplish?

If you're looking for a simple way to daemonize a perl script and give it a persistent interpreter to run in then Net::Server is a good solution. Also take a look at HTTP::Daemon, HTTP::Request, and HTTP::Response. Simple servers can easily be plugged together with these modules. Another good module is Net::Server::PreForkSimple.

Now that I re-read your question I may be completely off base. Is your situation a CGI script that you want to have communicate with your daemon for the purpose of grabbing some data? If so, then there are a few solutions. The best solution depends on the actual problem of course.

If the deamon needs to be a singleton and runs on the same box then IO::Socket::UNIX is probably a good way to go. If it doesn't need to be a singleton, e.g. you can spawn a daemon per server process, then perhaps IPC::Open3 since it's pretty fast for this type of thing.

If you're completely confused, sorry. Need a little bit more info.