[EMAIL PROTECTED] wrote: > I do not think it is a problem of LWP but Win32::GUI. because > when I used to run very similar procedure as a CGI script under > Apache web server, that is without Win32::GUI ,there were not > such problems.
woah! this is, perhaps, the most pure nonsense since the epoch ;-) CGI programming and GUI (or even 'proper') programming are two very different beasts. you just can't compare them. your CGI script did indeed 'freeze' just as your Win32::GUI script does, but you were on the other side of an HTTP connection, so you didn't noticed this (in fact, staring at the browser waiting for data to come is the CGI equivalent of 'freezing' :-). but in this case, there is no 'other side', so your whole program is blocking (thus no UI -- user interaction) while LWP is working. this is not a problem of LWP, neither a Win32::GUI one. the real 'problem' here is in the programming approach. you need to perform two tasks in parallel (UI and LWP fetching its stuff), so guess what you need? multithreading! try this: perldoc -f fork perldoc perlfork not the easiest thing in the world, but this is the right way. cheers, Aldo __END__ $_=q,just perl,,s, , another ,,s,$, hacker,,print;
