[EMAIL PROTECTED]">Hello Daniel,Ryan Hoegg <[EMAIL PROTECTED]> writes:Hello all,
Well, I have made it past authentication with this interesting service
provider of mine, and now I have to actually do something useful!
Well, it turns out that I need to maintain session state to do
anything. And how else to accomplish this than with cookies!
So I guess I need to extend the client code to support cookies.
Someone please tell me if these types of changes (dealing with HTTP
communication rather than XML stuff) are outside the scope of the
project.
I'd merge in patches adding improved HTTP support, but really think
that you'd be better off just running the server behind a Servlet in
Tomcat or Catalina (which both already have good support for this type
of thing).
Thanks for the pointers, you just cost me almost an hour of research time on jakarta.apache.org. =)
Actually, the project I am working on is IMHO a fairly good case for building more extensive HTTP client features into the XML-RPC project. I do not have a Tomcat server available and need to do some one-off work against some data that is accessible through a documented XML-RPC interface. At this point, I think it is overkill to assemble a Tomcat server, considering that I just need to use XML-RPC as a means for cleaning up some data and also considering that I have no experience with Tomcat.
I imagine there are others out there who just need an XML-RPC client and don't want to get into Tomcat. And unfortunately there are XML-RPC servers out there who use HTTP User-Agent headers and cookies as a part of their API.
Am I over-rating the complexity of a Tomcat setup?
Ryan
