Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #10764
| From | Gelonida N <gelonida@gmail.com> |
|---|---|
| Subject | m2crypto https, xmlrpc, keep_alive |
| Date | 2011-08-02 23:39 +0200 |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1803.1312321193.1164.python-list@python.org> (permalink) |
Hi, Just started playing with m2cryptos xmlrpc The code I'm is: import xmlrpclib from M2Crypto.m2xmlrpclib import Server, SSL_Transport from M2Crypto.SSL.Context import Context ctx = Context() # modify context svr = Server(rpc_url, SSL_Transport(ctx), encoding='utf-8') svr.mymethod1(1) svr.mynethod2(2) What I wondered is following. Will each RPC call go through all the ssl negotiation with certificate verification, etc? If yes, is there something like the concept of a keep_alive connection, that would avoid this overhead? If yes. What would I have to change in my above code. Thanks in advance for some ideas
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
m2crypto https, xmlrpc, keep_alive Gelonida N <gelonida@gmail.com> - 2011-08-02 23:39 +0200
csiph-web