[sr-dev] xmlrcp request takes very long time
Juha Heinanen
jh at tutpro.com
Mon Jul 6 21:39:27 CEST 2009
Andrei Pelinescu-Onciul writes:
> We could also close the connection in sr, but that would require
> additional code and it's the xmlrpc lib that's broken (parsing the
> answer only on close()
> is really braindamaged). However if there are lots of applications
> relying on the broken behaviour, I might be convinced to add the close
> option in sr xmlrpc.
well, python and php both are very popular for writing management
software and a basic xmlrpc client written in either does not work with
sr xmlrpc module. they do work with k mi_xmlrpc module which makes
migration from mi_xmlrpc to xmlrpc module painful.
i would suggest to do whatever is necessary make this simple call work:
server_path = XMLRPC_PROTOCOL + '://' + XMLRPC_SERVER + \
':' + str(XMLRPC_PORT) + XMLRPC_DIR
c = xmlrpclib.ServerProxy(server_path)
if you look at any examples on the web on python xmlrpc clients, the
above is what you will find. if sr requires something more complicated,
it is not a good idea.
-- juha
More information about the sr-dev
mailing list