[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlrpc-user
Subject:    RE: when implementing redirects xml-rpc content is lost
From:       "Andrew Norman" <anorman () piczoinc ! com>
Date:       2007-02-09 23:51:32
Message-ID: 1E6F4132F951A144B46329DDE805483501DDD8A1 () GOTHAM ! corp ! piczo ! com
[Download RAW message or body]

Anyone have any thoughts or comments to implementing xml-rpc redirects 
in the Apache XMLRPC client?

I have a jira ticket (XMLRPC-132) with proposed code changes (in an
eclipse patch file 

In this proposal, the XMLRPCStreamTransport class adds a customization
point to determine if the transport needs to redirect the request before
attempting to parse the response from the server. This uses a similar
redirect algorithm as used in the Apache Http client to processing
redirects with a Max limit to prevent a recursive loop.

The redirect logic itself is implemented in two callback methods
isRedirectRequired() and 
resetClientForRedirect()

These callback methods are only implemented in the
XmlRpcCommonsTransport which means that the other transport options
won't support redirects (unless they are subsequently modified to do
this by
implementing these inheirited 2 callback methods in their related
classes. 

-Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: xmlrpc-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: xmlrpc-dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]