The above should all happen within the same process, so I’m not sure where you’re coming from regarding forking.
WWW::Curl::Multi, as far as I can tell, uses curl’s internal select-based event loop exclusively, which won’t be as efficient as platform-native polling methods like epoll or kqueue. It appears to mimic the C API pretty closely, much like Net::Curl::Multi.
Do you mind clarifying what you see as “not so easy” regarding adding more URLs to the request queue?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi!
The above should all happen within the same process, so I’m not sure where you’re coming from regarding forking.
WWW::Curl::Multi, as far as I can tell, uses curl’s internal select-based event loop exclusively, which won’t be as efficient as platform-native polling methods like epoll or kqueue. It appears to mimic the C API pretty closely, much like Net::Curl::Multi.
Do you mind clarifying what you see as “not so easy” regarding adding more URLs to the request queue?