On 21-Jun-2001 Matt Cashner wrote:
> On Thu, 21 Jun 2001 [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.
> 
> um um i call post_respond.  am i bad monkey?

post_respond is IKC::ClientLite only, which is a blocking client for
embeding in "small" perl-spaces, like mod_perl...  Or am I missing
something obvious?

Also, I want IKC to be transparent.  IE, if $sesion is an opaque way of
specifying a session (either an alias, IKC specifier or reference), 
        $kernel->post($session=>'event', .....) 
should be totaly transparent.  post() works because of subscriptions, but
doing something like call() can never work.  I want a way that would do
the equivalent easily.

        $kernel->mutter($session=>'event', 'return_event', ....)

-Philip

Reply via email to