与PHP守护进程通信的最有效方法是什么？ [关闭]

Question

I did some PHP daemon and now I want my PHP webapp to communicate with it, e.g. send XML document to it and receive response after some time. As I would like to avoid file operations over the network (as it involves FTP), what would be the ideal way of sending this document? The PHP daemons and PHP webapps are on different servers. I have investigated various options so far:

• ActiveMQ, but that adds additional bloatware
• TCP Sockets (however it's hard to do it as the PHP daemon is single-threaded and very busy sometimes)
• FTP, SCP to send the file
• NFS / CIFS
• Using database

If the messaging server looks like the best option, what would be best suited for PHP? I would like to avoid centralized, single messaging server because it's difficult to approve firewall rules, and the network is very big, complex and very fail-prone. So that would require star-shaped network of messaging servers, and because of that they would need to very lightweight, easy to deploy and with no difficult dependencies.

Answer 1

The answer is obvious: Use TCP but don't use a single threaded programming language for a TCP daemon.

If you want to use PHP for the workers, maybe because you wish them to use a shared PHP library, you can code a most minimal daemon in a programming language which supports threads, and forwards the requests to PHP helper scripts (or pooled, single threaded TCP daeamons if you want to deploy the workers on different hosts, which is good for scalability)

However, a software which fulfils the requirements exists already: Gearman