On Thu, Jun 21, 2001 at 04:55:46PM -0400, [EMAIL PROTECTED] wrote:
> I hate call(). I really do. It makes code un-POE-like. And it can't
> work w/ IKC. However, it's really the best way to get an answer back. In
> IKC, you have to do $kernel->post(IKC=>'call', $specifier=>[params],
> 'callback_state') but this isn't compatible with session subscription.
Here are the related issues I'm documenting in TODO:
1. Yield must die.
a. Rename the bastard.
b. Maybe move it to $session->post()
2. Call should be depreciated, possibly rewritten, and maybe even
moved elsewhere.
a. Call between sessions is evil and should go away.
b. So call() becomes something which defaults to the current session.
c. Like yield().
d. Which is also evil and should go away.
e. So perhaps $session->call()
3. POE::Message (or POE::Event) is a good thing.
a. It can encapsulate named parameters instead of the vaguely icky
ARG0..ARG9.
b. It can encapsulate several postbacks, including refcounts which
keep the sender alive.
c. It can encapsulate inter-Kernel routing, messaging, and
directory services.
d. It can encapsulate automatic postbacks and exceptions.
Have I missed anything?
-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
