01-06-22 02.04, skrev [EMAIL PROTECTED] p� [EMAIL PROTECTED] f�ljande:
>> On Thu, Jun 21, 2001 at 04:55:46PM -0400, [EMAIL PROTECTED] wrote:
>
>> call() sucks, but it lets wheels pass on their synchronous input
>> events to the sessions which own them. As far as I know, that's the
>> only valid reason to use it.
> Oh. True. Hadn't thought of this.
>
>> Not entirely true. I use it extensively in the crossword server xwws
>> (somewhere at poe.perl.org), but I'd rather not have had to. Now that
>> postbacks exist, the mere act of sending an event can keep the sender
>> alive at least until it's delivered.
>>
>> Although postbacks across the inter-process boundary are going to fail
>> unless the gateway component holds onto them.
>
> Postbacks use closures and coderefs, objects that don't travel well.
> B::DeParse won't save us here, because the far end might be perl 5.004...
> or a completely different language, eventually.
Do they realy need that, can't we have a postback that just encodes
destination of the return and keeps a refcount to it so it won't go away
until it is sent back?
Artur
