Re^2: LWP::UserAgent timeout

I'd just add that, in either case, given that you are dealing with a GUI, it's usually a best practice to use a separate thread for the UI events processing and another for the processing:

LWP::UserAgent::timeout() it's a lower bound: "The requests is aborted if no activity on the connection to the server is observed for "timeout" seconds.This means that the time it takes for the complete transaction and the request() method to actually return might be longer."
Depending on what you do when you # deal with $response there are good chances you'll end freezing again your UI

Comment on Re^2: LWP::UserAgent timeout Download Code

Replies are listed 'Best First'.
Re^3: LWP::UserAgent timeout by IB2017 (Pilgrim) on Dec 17, 2018 at 17:42 UTC
Multi-threads, i.e. separating UI and other stuff, make sure sense. However, it frightens me turning my application in a multi-threads one. My GUI is Tk and Tk is said to be "not thread safe". Zero experience on my side.	[reply]
Re^4: LWP::UserAgent timeout by tybalt89 (Monsignor) on Dec 17, 2018 at 22:36 UTC
Look at `Tk::IO`	[reply] [d/l]
Re^4: LWP::UserAgent timeout by markong (Pilgrim) on Dec 17, 2018 at 21:39 UTC
Not only it does make sense, it is also necessary if you want a "snappy" UI: there is plenty of information on the topic (https://www.perlmonks.org/?node=Tk+thread), many discuss exactly what you're trying to achieve, e.g.: PerlTk on a thread... Need help in using threads in Tk	[reply]
Re^4: LWP::UserAgent timeout by bliako (Abbot) on Dec 18, 2018 at 00:57 UTC
I will second the multi-thread model if you have heavy calculations or a fair amount of other networking. I was under the impression that your only network interaction would be the one you showed. However, I have zero knowledge of Tk myself.	[reply]