在c++中的Linux守护进程来处理PHP请求-LinuxDaemoninC++toprocessPHPrequests

1  

Its better that u can use the php socket library to connect with the daemon running in your system and then u can pass data to the daemon and can process the result sent back by the daemon .

最好使用php套接字库连接系统中运行的守护进程，然后将数据传递给守护进程，并处理守护进程发回的结果。

You can refer the PHP Socket Library for creating code to do socket connection with daemon ...

您可以参考PHP套接字库来创建与守护进程进行套接字连接的代码……

I think this is a better option than using CURL as the daemon is also a custom socket interface , CURL will be most suitable for HTTP request's , but i think here the daemon is not an HTTP one..

我认为这是一个比使用CURL更好的选择，因为守护进程也是一个定制的socket接口，CURL将最适合HTTP请求，但是我认为这里的守护进程不是HTTP请求。

2  

Question is rather confused.

问题是,而困惑。

I need to create a daemon(process) for Linux using C/C++

我需要使用C/ c++为Linux创建一个守护进程(进程)

Why does it have to be written in C or C++?

为什么一定要用C或c++写?

I have also read a little about PHP daemons, but I'm not sure whether they are applicable

我也读过一些关于PHP守护进程的文章，但是我不确定它们是否适用

Does that mean it doesn't need to be written in C/++? Why do you think they might not be applicable?

这是否意味着它不需要用C/+来写?为什么你认为它们可能不适用?

the daemon will parse the XML using Xerces

守护进程将使用Xerces解析XML

Why does it have to use Xerces? Presumably the daemon is supposed to do something more than just parse XML and compose a response - what else does it do?

为什么要使用Xerces?想必守护进程应该做的不仅仅是解析XML和组成响应——它还做什么呢?

Writing a daemon is not a trivial process. Writing a socket server is not a trivial process. It is somewhat simplified by implementing a well defined protocol at each end.

编写守护进程并不是一个简单的过程。编写套接字服务器不是一个简单的过程。通过在每个端点实现一个定义良好的协议，可以稍微简化它。

...which rather begs the question, why not just use HTTP as the protocol and a webserver to implement the server stuff, and seperate the application-specific logic into a [f]CGI program. And taking this one step further, why not implement the application-specific logic using PHP.

…这就引出了一个问题，为什么不直接使用HTTP作为协议和webserver来实现服务器，并将特定于应用程序的逻辑分离到一个[f]CGI程序中呢?更进一步，为什么不使用PHP实现特定于应用程序的逻辑呢?

The only thing hard and fast is the results i.e succesful communication between the PHP pages and the daemon

唯一困难和快速的是结果i。PHP页面和守护进程之间的成功通信

Some options:

一些选项:

1. Write the application specific part as a PHP page then invoke it via an HTTP request using curl

   将应用程序特定的部分作为PHP页面编写，然后使用curl通过HTTP请求调用它

2. Write the server as a single tasking stdio server and use [x]inetd to invoke it, handling the client side connection as a network socket (requires that you define your protocol)

   将服务器编写为单个任务stdio服务器，并使用[x]inetd来调用它，将客户端连接作为网络套接字处理(要求您定义您的协议)

3. Write a forking server daemon in PHP handling the connection at both ends as a network socket (requires that you define your protocol)

   用PHP编写一个分叉服务器守护进程，以网络套接字的形式处理两端的连接(需要定义协议)

4. write a single threaded server daemon (using socket_select) in PHP handling the connection at both ends as a network socket (requires that you define your protocol)

   在PHP中编写一个单线程服务器守护进程(使用socket_select)，以网络套接字的形式处理两端的连接(需要定义协议)

Of course anywhere I've mentioned PHP above, you could equally use C, C++, Perl, Java....etc.

当然任何地方我上面提到的PHP,您同样可以使用C、c++、Perl、Java ....等等。

0  

xinetd / inetd might be a bit old skool but can make this easy and scalable (with in limits)

xinetd / inetd可能有点老了，但是可以使它更容易扩展(具有限制)

Inetd will call you program and send the the traffic to stdin and your stdout will go to the connection. As long as you dont need shared information it stops you having to worry about making the program bug free/no memory leaks etc....

Inetd将调用您的程序并将流量发送到stdin，您的stdout将进入连接。只要你不需要共享信息停止你不必担心程序缺陷/不自由内存泄漏等....

Simon Loader

西蒙装载机