"Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]> writes:
> 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.
This sounds useful. What are the specific benefits of using this
vs. using vanilla XML-RPC handlers?
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
