Thrift 异步函数中的回调?

Roberto, unfortunately the Thrift framework has no such built-in functionality. There may be a number of alternatives, though, depending on what you want your PHP client session to do during the time you would normally have waited for the computationally-intensive Thrift server to answer (had you not used oneway.)

我现在只能想象，如果您编写了一个 Web 应用程序，其中一个用户(或多个并行用户)可以触发计算密集型任务，您想提供一些反馈在所述任务不断进行的同时向所述用户发送.

I can only imagine, for now, that you are in a situation where, having coded a web application where a user (or several users in parallel) can each trigger a computationally-intensive task, you would like to provide some feedback to said users while said tasks churn along.

从一开始，您就完全正确地试图避免您试图避免的解决方案.您的 PHP 客户端会话无法在不阻塞的情况下为回调接口提供服务(除非您尝试使用 pcntl_fork 或其他一些PHP 线程创可贴.)

From the start, you are absolutely right in trying to avoid the solution that you are trying to avoid. Your PHP client sessions cannot service a callback interface without blocking (unless you dig your hole even deeper by trying to use pcntl_fork or some other PHP threading band-aid.)

最简单和恕我直言最好的方法是两个从事件驱动模型切换(我想在服务器完成时收到通知)轮询模型(我会定期询问服务器是否完成.)有几种实现轮询模型的方法，服务器上也有多种实现选项在客户端，例如:

The simplest and IMHO best way out of this is two switch from an event-driven model (I want to be notified when the server is done) to a polling model (I will periodically inquire with the server whether or not it is done.) There are several ways of implementing a polling model, with multiple implementation options on the server as well as on the client sides, such as:

1. 在调用阶段:

• PHP 客户端会话分配一个唯一的 job_id 值；然后会话使异步 oneway 调用 void compute(..., job_id) 到计算密集型 Thrift 服务器，

• the PHP client session allocates a unique job_id value; the session then makes the asynchronous oneway call void compute(..., job_id) to the computationally-intensive Thrift server,

-- 或 --

• PHP 客户端会话对计算密集型 Thrift 服务器进行同步调用job_id start_compute(...)；服务器分配唯一的 job_id 值，然后在单独的线程/进程中生成实际的计算密集型任务，使用分配的 job_id<立即返回到 PHP 客户端会话/li>

• the PHP client session makes a synchronous call job_id start_compute(...) to the computationally-intensive Thrift server; the server allocates the unique job_id value, then spawns the actual computationally-intensive task in a separate thread/process, returning right away to the PHP client session with the allocated job_id

在计算阶段:

• PHP 客户端会话通过对计算密集型 Thrift 服务器的同步 status get_status(job_id) 调用，定期检查计算密集型作业的状态，

• the PHP client session proceeds to periodically check the status of the computationally-intensive job via a synchronous status get_status(job_id) call to the computationally-intensive Thrift server,

-- 或 --