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

Groups > comp.lang.python > #10764

m2crypto https, xmlrpc, keep_alive

Path csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!feeder.news-service.com!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path <python-python-list@m.gmane.org>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.004
X-Spam-Evidence '*H*': 0.99; '*S*': 0.00; 'context': 0.04; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:80.91.229.12': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'received:lo.gmane.org': 0.09; 'server,': 0.12; 'etc?': 0.16; 'subject:https': 0.16; 'xmlrpclib': 0.16; 'advance': 0.18; 'modify': 0.22; 'code.': 0.22; 'wondered': 0.23; 'code': 0.24; "i'm": 0.27; 'import': 0.29; 'xmlrpc': 0.30; 'yes.': 0.30; 'thanks': 0.31; 'hi,': 0.31; 'to:addr:python-list': 0.34; 'header:X-Complaints-To:1': 0.34; 'header:User-Agent:1': 0.34; 'there': 0.34; 'ssl': 0.35; 'some': 0.37; 'received:org': 0.38; 'something': 0.38; 'header:Mime-Version:1': 0.39; 'to:addr:python.org': 0.39; 'concept': 0.73; 'connection,': 0.73; 'following.': 0.91
X-Injected-Via-Gmane http://gmane.org/
To python-list@python.org
From Gelonida N <gelonida@gmail.com>
Subject m2crypto https, xmlrpc, keep_alive
Date Tue, 02 Aug 2011 23:39:39 +0200
Mime-Version 1.0
Content-Type text/plain; charset=ISO-8859-1
Content-Transfer-Encoding 7bit
X-Gmane-NNTP-Posting-Host unicorn.dungeon.de
User-Agent Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 ""
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.12
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.1803.1312321193.1164.python-list@python.org> (permalink)
Lines 32
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1312321193 news.xs4all.nl 23974 [2001:888:2000:d::a6]:57396
X-Complaints-To abuse@xs4all.nl
Xref x330-a1.tempe.blueboxinc.net comp.lang.python:10764

Show key headers only | View raw

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

Thread

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

csiph-web