Christopher Elkins wrote:
> The main point here is that "do whatever else you want" would be identical
> in both cases. It is just that XMLRpcServiceManager or whatever would
> "behind the scenes" be massaging your input into RPC calls.
>
I've been thinking about the XML-RPC and I have a question. Maybe a
dumb one
but I'll ask it anyway -
How will Turbine decide between handling a request as an XML-RPC call
or just a normal request?
Are you looking for a URL such as - POST /XMLRPC HTTP/1.1
and that always gets routed to the XMLRpcServiceManager?
Or are you looking for content type ( e.g text/xml )? Off the top of
head,
content type would screw up any future Turbine-Cocoon integration.
dave
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
