On 6-Feb-07, at 7:20 AM, [EMAIL PROTECTED] wrote:
Ok, I have some lengthy processes coming up in the near future.
Should I wait for the job server to be written or will I have to
implement the above?
Assuming the latter :)
Yeah :-(
If I were you I'd have some sort of job-server (mod_perl would be my
recommendation) that you call to entirely separately.
What does return CONTINUE do? I've read up on continuations. I presume
ax2 is storing the stack or somesuch and waiting for an interrupt
from danga?
How does it continue from where I did a return CONTINUE? Or do I
have to
somehow program that in?
So you return YIELD from a hook and it suspends the plugin stack (not
the execution stack as that would require core perl support for
continuations). You then have to have some kind of event fired from
the event loop - either a timeout or a socket event or something that
calls $client->finish_continuation - that then picks up at the NEXT
registered hook/plugin. So if you want that to be within your own
plugin you need to register multiple hooks for the same phase. See
plugins/aio for examples.
Note: "return CONTINUATION" is used in the examples but that's about
to be deprecated in favour of "return YIELD" which is more
syntactically correct.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
