Re: [Exist-development] Execution Pipeline, async xquery execution...

[Thomas W. <tho...@gm...>]

Andrzej and Adam,

I would like to thank you both for helping me to see the simple solution 
that was right in front of my nose :-)

Thomas

----- Original Message ----- 
From: "Andrzej Jan Taramina" <an...@ch...>
To: "Thomas White" <tho...@gm...>
Cc: "Adam Retter" <ad...@ex...>; 
<exi...@li...>
Sent: Thursday, February 04, 2010 2:34 PM
Subject: Re: Execution Pipeline, async xquery execution...


> Thomas:
>
>> I think the opposite way - this is generic functionality. It is an
>> equivalent of BREAK in FOR loop.
>
> Beware of mixed metaphors.  Scheduled jobs and schedulers are not the same 
> as language design constructs.
>
> And since it's not that hard to implement what you need with existing 
> functionality, my vote stays at -1. ;-)
>
>> One more thing. When we have an asynchronous function it is very
>> common to have a callback function that is called at completion of the
>> main function. If we have an option to pass a callback function when
>> we schedule an XQuery function, this will allow us to do post
>> processing on the results.
>
> The question with an async XQuery call is callback to where?  Right now, 
> there is no way to guarantee that the
> initiating XQuery is still running (XQuery being a sort-of, more or less, 
> functional language).
>
> Having your async XQuery (initiated using the Scheduler functions) call a 
> separate XQuery at the end to do post
> processing is not that difficult.
>
> -- 
> Andrzej Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com
>