From: Conrad S. <co...@he...> - 2002-04-19 15:11:11
|
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). Yes, xmlrpc-c is also unsupported AFAIK as Eric is busy with other things. Also, I wrote a simple client to my py-xmlrpc/apache-based server last night (oh the joys of jet-lag ;-) and found it seriously lacking performance - on my laptop connecting to a localhost server my python-based client does about 130 connections/sec, while the xmlrpc-c client does only 16/sec. > > 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. Sounds good. Cheers Conrad > > 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 -- |