Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

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

by Anonymous Monk
on Sep 24, 2012 at 15:12 UTC ( #995409=note: print w/replies, xml ) Need Help??

in reply to Re^3: Thread::Queue and WWW::Curl
in thread Thread::Queue and WWW::Curl

When I run via threads, the following line does not output to my terminal:

print "\nresponse was $response";
, 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).

Replies are listed 'Best First'.
Re^5: Thread::Queue and WWW::Curl
by BrowserUk (Pope) 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

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; ...

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://995409]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (3)
As of 2018-01-18 12:05 GMT
Find Nodes?
    Voting Booth?
    How did you see in the new year?

    Results (211 votes). Check out past polls.