on 5/31/01 2:53 PM, "Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]>
wrote:
> 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?
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.
It should.
> 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?
Correct. It doesn't really make much sense to have more than one server
running IMHO.
> Is this (having a single listening port) the usual approach when
> writing XML-RPC servers?
I would say so.
> 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?
Just run the XML-RPC HTTPd on your own.
> 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?
You can put a proxy in front of the XML-RPC server to balance the load.
-jon
--
"Open source is not available to commercial companies."
-Steve Balmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
