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

[Adam R. <ad...@ex...>]

Perhaps it is also interesting to consider the development of a pragma -

(# exist:thread #){

(: asynchronous xquery code :)

}

On 2 February 2010 16:15, Andrzej Jan Taramina <an...@ch...> wrote:
> Thomas asked:
>
>>>  do believe, having asynchronous mechanism for fetching data in eXist will
>>> > give us foundation for many?interesting new?ideas.
>>> > I will need this functionality in about two months time and I?really hope
>>> > somebody from the dev team will be interested in implementing the execution
>>> > pipeline.
>
> To which Adam replied:
>
>> I think we will be very pushed for time to meet that deadline. The
>> roadmap for the next two versions is already laid out - although it is
>> subject to change.
>
> This feature, asynchronous execution of XQueries, is something that I'm really interested in having as well.
>
> And I'm willing to implement this within the next two months (probably sooner than that!).
>
> I was thinking of a new function along the lines of:
>
>        util:eval-async( ... )
>
> which would return some sort of id for the spawned xquery that could be used to check completion status and obtain the
> results of the execution. Same function signatures as the original util:eval() function to start.
>
> Would this kind of new function meet your needs as well, Thomas?
>
> Thoughts from the crew on such a new function?
>
>
> --
> Andrzej Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb