|
From: Bill E. <bi...@rf...> - 2002-08-02 17:56:46
|
Okay, the performance issue seems to have been DNS-related that oddly came up in the 4 minutes between running query.py and my interface, so now my XMLRPC interface is pretty snappy. I still would like to be have the overwrite=1 option from XMLRPC using strings - I can easily add another Java class in RpcAPI to do this but it seems that should be there anyway. Bill Eldridge wrote: > > Seems the RpcAPI.java changed a bit, > and what used to accept > > parse(String xmlData,String docName,overwrite=1) > > is now only: > > parse(String xmlData,String docName) > > or > > parse(byte[] xmlData, String docName) > > Is that true, and does this make sense > to not let a string overwrite? If so, > do you know of a Python method to convert > the string to appropriate XMLRPC byte code? > (would this be a xmlrpc.encode() or something? > > Also, comparing your query.py which uses > port 8088, and mine which uses XMLRPC port 8081, > yours runs at about 5 times the speed of mine. > Presuming I'm not doing something stupid, > is there a big inherent difference between > using the HTTP & XMLRPC methods? > > Thanks, > Bill > -- Bill Eldridge Radio Free Asia bi...@rf... |