Hi, I believe as soon as you call socket.setdefaultimeout it also changes certain behavior for ALL sockets in general (blocking non blocking etc) plus obviously the timeout. That is in my opinion pure evil(TM) because surely database drivers, connection handlers, logging tools and god knows what will never have the same expectations as to how the sockets should behave. I didn't find a way to set a timeout for a specific connection when using urllib, urllib2 or even httplib - in python 2.3. So I ended up using raw sockets :-( because then it is possible to set a custom timeout without changing behaviour of all the other sockets.
BTW If anybody knows a better way to do this I would not mind learning a trick or two :-), because reimplementing HTTP 1.0 GET request was a breeze, but if I had to re-implement https with authentication I'd be one unhappy coder. Jakub On 2/20/06, Ned Batchelder <[EMAIL PROTECTED]> wrote: > > The value was 20 (the unit is seconds). With the function call > removed, the calls completed successfully in much less time than 20 > seconds, on the order of 1 second, so I don't thing the timeout was > actually kicking in. > > --Ned. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
