Re^3: Thread::Queue and WWW::Curl

You still haven't said what fails? Or how you know something is failing?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^3: Thread::Queue and WWW::Curl

Replies are listed 'Best First'.
Re^4: Thread::Queue and WWW::Curl by Anonymous Monk on Sep 24, 2012 at 15:12 UTC
When I run via threads, the following line does not output to my terminal: `print "\nresponse was $response";` [download] , nor does the print statement after it output; furthermore I don't see the user deleted on the remote server when running via threads (however I do when running that code without threading).	[reply] [d/l]
Re^5: Thread::Queue and WWW::Curl by BrowserUk (Patriarch) on Sep 24, 2012 at 15:48 UTC
Looks like a clear-cut case of either WWW::Curl or libcurl not being thread-safe. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. RIP Neil Armstrong	[reply]
Re^5: Thread::Queue and WWW::Curl by Anonymous Monk on Sep 24, 2012 at 15:45 UTC
Apologies, I omitted two use statements in the above hitFbNew subroutine, amended as follows: `sub hitFbNew { my ($method, $endpoint, $form) = (shift, shift, shift); use WWW::Curl::Easy; use WWW::Curl::Form; my $curl = WWW::Curl::Easy->new; my $curlf = WWW::Curl::Form->new; ...` [download]	[reply] [d/l]