Re: [py-xmlrpc-devel] CVS archive

[Conrad S. <co...@he...>]

Hi Shilad

I started looking at ehs, and adding at one feature that I need: namely
simple authentication.

Attached is a patch that adds simple authentication headers to a
request. It works here, but the transport may have to handle 401
responses (authentication required) more gracefully.

The patch modifies the file examples/xmlrpc_client_example.c to use
authentication, but this should probably become a separate example.
Also, please look at the changes in http/ where the pasword and username
gets base64 encoded, I'm not sure who owns returned strings for some of
the calls, so it may leak memory in its current implementation.

Comments welcome!

Conrad

On Thu, 2002-04-18 at 16:12, Shilad Sen wrote:
> Conrad,
> 
> I'm glad to here that you find the library useful.
> 
> The main motivation for ehs was so that we could write services inhouse in C
> that are fast.  I took a look at several other options of C libraries... for
> xml-rpc I looked at epinions and Eric Kidd's versions.
> 
> Eric Kidd's xmlrpc library is pretty closely tied into libwww, which I
> dislike (it's a bit big and clunky for my tastes).
> 
> Epinions library is quite good, but I would need to code my own transport
> libraries.  There is no really good C server library that fits nicely into
> complicated event handling programs (that I've found).
> 
> So that's the motivation.
> 
> As far as significant features...
> 
> - I plan on including better support for HTTP including HTTPS, different
> encodings, etc.
> - I'll include an OPTION to use expat as the parser
> - It will be available as a standalone C library for C programs, or other
> languages can have C bindings
> - It will be COMPLETELY backwards compatible with the xmlrpc.py module
> 
> I'm even thinking about trying to go down the soap path, although I know
> that will involve writing a schema validator.
> 
> I actually think now that I may release another version or two under the
> old codebase, though.
> 
> Shilad
> 
> 
> > 
> > Hi Shilad
> > 
> > What are the motivation/significant features of ehs?
> > 
> > Btw, I use py-xmlrpc every day and having gone through doing xmlrpc in
> > C++ in the last two days\I appreciate it even more ;-)
> > 
> > Cheers!
> > 
> > Conrad
> > 
> > On Fri, 2002-04-12 at 07:22, Shilad Sen wrote:
> > > Hello,
> > > 
> > > I finally got around to setting up a cvs archive for the py-xmlrpc library.
> > > 
> > > There are two packages available. Py-xmlrpc, is the latest (unstable)
> > > release under the old codebase.  Ehs is the latest (really unstable) new
> > > codebase.  Please peruse the new codebase and let me know what you think.
> > > 
> > > You can download the NEW stuff by running the following commands (for redhat
> > > bash users).
> > > 
> > > export CVS_RSH=ssh
> > > cvs -d:pserver:ano...@cv...:/cvsroot/py-xmlrpc co ehs
> > > 
> > > if you want to get the old codebase for any reason, the you would use:
> > > 
> > > cvs -d:pserver:ano...@cv...:/cvsroot/py-xmlrpc co py-xmlrpc
> > > 
> > > The new codebase is far along, but not well documented.  I need suggestions on
> > > it!
> > > 
> > > Shilad
> 
> _______________________________________________
> py-xmlrpc-devel mailing list
> py-...@li...
> https://lists.sourceforge.net/lists/listinfo/py-xmlrpc-devel
-- 
*-----------------------------------------*
| Conrad Steenberg                        |
| Caltech, Mail Code 356-48               |
| Pasadena, CA, 91125                     |
| e-mail: co...@he...          |
| Tel: (626) 395-8758                     |
*-----------------------------------------*