Thanks.  But that's not what I was asking.  The vendor is claiming that
their system would have worked fine had we used Apache XML-RPC 2.0
rather than 3.0.  I don't believe it.  I find nothing in the current
state of 2.0 that looks remotely like it handles redirection.  Do you
agree with me?

If we are going to get into patching, it will be based on 3.0, not 2.0.
I have no desire to go back there.

-----Original Message-----
From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] 
Sent: Friday, July 20, 2007 1:44 PM
To: xmlrpc-dev@ws.apache.org
Subject: Re: [jira] Updated: (XMLRPC-132) Enabling the ability for the
xml-rpc client to redirect requests


On 7/20/07, COHEN, STEVEN M (ATTSI) <[EMAIL PROTECTED]> wrote:

> We are in a discussion with a vendor who claims that their product
> should handle redirection correctly when used with a client (that's
our
> role here) based on Apache XmlRpc 2.0.  I have been staring at the 2.0
> code for a while and I am unable to see anyplace in that code base
where
> redirection requests are handled.  As far as I can tell, Apache
XML-RPC
> has not handled redirection until the introduction of this patch after
> 3.0.  Can someone tell me if I am correct or point me at why this
would
> not have been a problem with 2.0?

The patch isn't too difficult. It should be quite easy to backport
this patch, or a similar functionality to 2.0, perhaps by subclassing
the commons-httpclient transport.

Jochen


-- 
"Besides, manipulating elections is under penalty of law, resulting in
a preventative effect against manipulating elections.

The german government justifying the use of electronic voting machines
and obviously  believing that we don't need a police, because all
illegal actions are forbidden.

http://dip.bundestag.de/btd/16/051/1605194.pdf

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to