Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #10764 > unrolled thread

m2crypto https, xmlrpc, keep_alive

Started byGelonida N <gelonida@gmail.com>
First post2011-08-02 23:39 +0200
Last post2011-08-02 23:39 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python


Contents

  m2crypto https, xmlrpc, keep_alive Gelonida N <gelonida@gmail.com> - 2011-08-02 23:39 +0200

#10764 — m2crypto https, xmlrpc, keep_alive

FromGelonida N <gelonida@gmail.com>
Date2011-08-02 23:39 +0200
Subjectm2crypto https, xmlrpc, keep_alive
Message-ID<mailman.1803.1312321193.1164.python-list@python.org>
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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web