That's enough for an introduction. Good resources for information are:
In PHP (and other languages if I get the need/chance to port it) you have another Engine object, where you register your functions/methods. These can be either regular functions/methods defined by the user, or can be specially prepared to receive certain parameters, in this way you can receive a lot more information, mainly about the environment and in turn have better error handling. Your function/method works with the information and returns the result/error. This result is packed with the transaction reply, and sent to the client.
There are provisions on both sides, to execute and monitor asynchronic transactions. These rely on a forking mechanism, MySQL tables for holding information, and a high level script for the monitoring. All this may seem a mess, but it is needed to overcome the limitations of a short lived PHP script, especially in Windows which lacks the interprocess communications available in other OSes. However, I haven't used that in production for anything yet, it was done purely for the pleasure of programming. Also, implementing this on another language may be easier.
If you have seen the other projects in my webpage, you may find a pattern. I don't have much time, and I always have several projects going on, and putting in place tidy code for publishing takes time. So some time in the future (a few months?) I plan to publish it here the whole code, with a manual. In the meantime, a big sorry , but if I can help you in something, just email me.
|< Prev||Next >|