My advice is to not deal with Coro::cede but to use a Coro-aware LWP::UserAgent implementation, for example Coro::LWP. Then you can just use async { ... } to launch your processing in a non-blocking fashion.
I don't understand why you want to use Coro (or forks::BerkeleyDB) - maybe you want to communicate the data you fetch via a database or files instead. That would make the communication much easier, see perlipc.
In reply to Re: Do I need to use Coro instead of threads/forks
by Corion
in thread Do I need to use Coro instead of threads/forks
by mohan2monks
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |