Graham Dumpleton
grahamd at dscpl.com.au
Sat Sep 17 07:25:42 EDT 2005
On 16/09/2005, at 3:24 AM, Zsolt Barat wrote: > Graham Dumpleton wrote: > >> Still using a separate backend service process or framework is still >> probably preferable, with the handlers using XML-RPC or some other >> messaging system mechanism to communicate with it. You still have the >> issue of having to ensure the backend service is started, but then it >> also means your backend service isn't really dependent on Apache and >> you could use other means to communicate with it. Ie., Apache just >> becomes one type of interface. >> > hi, > this is interesting. i just try to make something like this. a tiny > webapplication which connects to a serial port and issues some > datarequest. are they already some recommended frameworks (xml-rpc) you > aware of which deal with this issue? sample apps? Depends on your requirements and how complicated you need to make your server. Simplest means of making a standalone XML-RPC server is with the SimpleXMLRPCServer module supplied with Python. This may though not be adequate for an event driven system which needs to deal with a serial port as well as handle XML-RPC requests. A more complicated system which you might look at is Twisted. See: http://twistedmatrix.com/ It has all manner of stuff for building event driven systems and also has components for handling XML-RPC requests which can be used to drive and control other parts of the system. Graham
|