I've been using LWP with the timeout feature turned on and everything works
fine. There are about 5 different components in our entire application that
I'm using LWP for and in each instance, the timeout is set to a different
value based on the usage(for eg, a db-related call will need more time than
a simple GET or POST). And in each of the components, the caller of the API
sets his own timeout period too. And everywhere it works perfectly fine.
-Pramod
At 12:22 AM 8/9/00 -0700, [EMAIL PROTECTED] wrote:
>On 8 Aug 2000, at 18:25, [EMAIL PROTECTED] wrote:
>
>> I tried all sorts of timeouts and that never helped at all. I even threw
in a
>> ALARM which didn't have any affect unless I used a well known URL. I have
>> seen LWP waiting for over a hour on the URL. Around lunch time it did
respond
>> back after 5 mins with a error that it could not connect with a
>> $ua->timeout(10). A later attempt it just hanged for over 30 mins till I
>> killed it. Seems to me a lot of the timeout problems could perhaps be
solved
>> if one could understand what is happening with these various URLS and
their
>> server responses to make socket/select more responsive for a wider
variety of
>> URL's encountered since this is what LWP relies on for the connection.
>>
>
> If you don't mind, can you provide a few example urls? It sounds
>like we're running up against similar problems, except that our
>system is running the requisite 3 minutes before failing (so far).
>Unfortunately 3 minutes is still too long and I would like to reduce the
>timeout.
>
> Does anyone know if the timeout feature is being worked on?
>
> Regards
> Bob Minnick, Northern Webs
>
>^------------------------------------------------------------------------^
>| Bob Minnick, President, Northern Webs |
>| 159 Trapps Drive |
>| Sagle, ID 83860 |
>| 208.265.0474 |
>| http://www.northernwebs.com (homepage) |
>| http://www.northernwebs.com/set/setsimjr.html (meta medic) |
>^------------------------------------------------------------------------^
>
