Greeting All,

I am writing a Rails App which includes (I hope) an XMLRPC API
interface.  I am working with the XMLRPC library in Ruby 1.8.6 to write
a client and a Mock of the Rails server.  In looking at the code in the
Lib I have a few questions.

First, the documentation is sketchy in the client and server classes and
non-existent in the the supporting files.  I've made notes in my local
copy and would be happy to share them, if they would be appreciated.
There seems to be a lot of hidden functionality that is not documented.

Next, I need to authenticate the user, and there seem to be a number of
different ways to do this: HTTP Authentication, Cookies, or within the
RPC it's self.  This last is the one used in the two examples that come
with Rails, but I consider it suboptimal.  What is required for the
other two?  I read this: http://www.ruby-forum.com/topic/81539#140475
but I'm not clear on how the user information makes it from the caller
to my RPC function.

With stand alone XMLRPC server, is it possible to see the original HTTP
request object from within the handler block?

Finally, in client.rb lines 565 and 566 appear to handle cookies in a
very non-standard way:

c = resp["Set-Cookie"]
@cookie = c if c

It looks to me like having the server set a new cookie simply replaces
all the existing cookies.  My initial guess is that this was a hack to
make secessions work under Rails without having to completely support
cookies.  Can anyone shed some light here?

Thanks for the help.

J. F. Miller

-- 
Posted via http://www.ruby-forum.com/.