Re: persistent HTTP connections
Robert Ullmann <rlullmann <at> gmail.com>
2010-06-01 15:24:19 GMT
Thanks, I've coded it (very easily, somewhat less code than there was,
"urllib2" just makes things more complicated than the httplib I/F
Does the API put *really* want the text in the encoded URL? It does
work ... but isn't it sometimes kinda long?
On Tue, Jun 1, 2010 at 6:18 PM, Roan Kattouw <roan.kattouw <at> gmail.com> wrote:
> 2010/6/1 Robert Ullmann <rlullmann <at> gmail.com>:
>> I noted that MWclient uses, or tries to use, persistent HTTP
>> connections to the API.
>> I have a few questions, as I am looking at improving Interwicket,
>> which makes lots of API calls, and is sometimes driven nuts by the two
>> layers of proxies (here, on my side of the net) that are prone to
>> failing ...
>> Is using persistent connections a good idea?
> For requests made in rapid succession, definitely. For requests that
> are further apart, maybe.
>> What is the server-side timeout when a connection is idle?
> No idea. You could find out by trying :)
>> Can I make requests to various different projects (xx.wiktionary, for
>> various xx) on the same connection (looks like it, as they all return
>> the same address)?
> Yes, they all return the same IP address.
> Roan Kattouw (Catrope)
> Mediawiki-api mailing list
> Mediawiki-api <at> lists.wikimedia.org