Since nobody had any comments, here are my thoughts on something
that we are considering for our projects, and that might be useful
to add to Turbine: RemoteActions. How about a RemoteAction class,
inheriting from Action, that uses the XML-RPC service to invoke
a remote method somewhere else? I haven't really looked into it
in detail (plan to do that while at JavaOne), but it looks like
something potentially useful.
Even more, how about:
Action
+-RemoteAction
+-XMLRPCAction
+-SOAPAction
Another possibility is a single RemoteAction class, and configuration
that allows you to change the protocol on the fly.
Yet another possibility: the single RemoteAction class, and adding
Jon's suggestion to the XML-RPC service, where you could configure
or detect whether you want to use RMI instead of XML-RPC.
Thoughts? I would still like comments on my questions below. Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
> -----Original Message-----
> From: Diethelm Guallar, Gonzalo [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 31, 2001 5:54 PM
> To: '[EMAIL PROTECTED]'
> Subject: XML-RPC questions
>
>
> 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]
