XML-RPC interface

[Rob Brown-Bayliss]

> The 'slow' issue shouldn't be underesimated.  To display a transaction,
> you need to make dozens of calls: 'get date', 'get description' 'get
> amount', etc. etc.  If each call took even 100 millisecs, it would take
> a few seconds just to display one transaction.   If each call took
> only 10 millisecs, then it would take a few seconds to display ten
> transactions. Forget 100.

The way I would do it is have the xml-rpc server (the part that, if I
understant the engine correctly would be the client on the host machine)
make all these calls to the backe end, then send it over the network the
the xml-rpc client machine,  one network transaction, not dozens.

Though, the application I am developing is a little different in it's
requirements.  What I have is each store (will) run a linux box, each
pos being a X terminal (along the lines of www.ltsp.org).  The server in
each store caching the days transactions, and over night connecting the
the head office, and then esentially replicating the databases (I use
postgres as the backend for all stores).  I am already useing xml-rpc to
control the connections (so that each store knows if it needs to
download data etc)

Speed is not really an issue, but I do see your point. 

-- 

  Rob Brown-Bayliss
 ---======o======---