I would like to confirm my understanding of the XML-RPC service.
>From what I read, it seems to turn your Turbine app into an XML-RPC
server, which will listen to and service requests from clients.
In order to do this, you write a class implementing the methods
to be accessible via XML-RPC, and set your TR.props to have an
entry services.XmlRpcService.handler.<published name> pointing to
the class. That's for the server side. For the client side,
the service allows you to send an XML-RPC call to any server.
Is this correct? I'm asking because it doesn't seem clear to
me that the same service has functionality for both server and
client... Please correct me if I'm wrong.
Now, reading TR.props I get the impression you can only listen
for XML-RPC traffic on one port. Given that Turbine has the
philosophy of running everything as one single servlet, this
means I can only have one XML-RPC server in my Turbine app, right?
Is this (having a single listening port) the usual approach when
writing XML-RPC servers?
Something else: say all I want my app to do is handle XML-RPC
traffic; no HTTP, it won't be a servlet. Can I run my app in stand-
alone mode? Is that one valid example of using Turbine without a
servlet engine?
Finally, do XML-RPC and/or Turbine have any provisions for balancing
traffic? For example, if the app is getting LOTS of messages on the
same XML-RPC port, is it the app responsibility to distribute that
load somehow (for example, using an incoming and outgoing queue), or
are there external mechanisms to do that?
Thanks for any info,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
