Re: [xsl] XSLT 3.0 streaming vs other big-data technologies

Subject: Re: [xsl] XSLT 3.0 streaming vs other big-data technologies
From: "Dimitre Novatchev dnovatchev@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 14 Jun 2018 14:35:32 -0000
> Moving to 64 bits everywhere would be a significant challenge, not least
because of the difficulty of testing all paths with the large data volumes
needed to find the bugs.

Let's call this Saxon-64 :)

I believe we will live to see Saxon-64. And this would make it even
more *the* (only) XSLT processor people like me will be using.

Other features that would be great:

  - producing streamed output

  - accept and process the "initial match selection" as a stream

  - asynchronous processing -- something like "promise" in Javascript

Cheers,
Dimitre



On Thu, Jun 14, 2018 at 12:58 AM, Michael Kay mike@xxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Simply moving to a 64-bit long would allow an InputStream that would take a
million years or so to process, which is infinite enough for most people.
>
> This particular limit is easy to fix. There are others that are harder:
32-bit limits on the size of sequences and strings are scattered throughout
Saxon not to mention the Java VM itself. One example: a streamable stylesheet
can call position() to get the position of the current node, and position() is
a 32-bit int. Similarly xsl:number uses 32-bit integers. Moving to 64 bits
everywhere would be a significant challenge, not least because of the
difficulty of testing all paths with the large data volumes needed to find the
bugs.
>
> Michael Kay
> Saxonica
>
>
> On 14 Jun 2018, at 06:19, Mukul Gandhi gandhi.mukul@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Hi Mike,
>
> On Wed, Jun 13, 2018 at 1:00 PM, Michael Kay mike@xxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>>
>> The Saxon implementation does have some limits that mean the input stream
can't be infinite: most obviously, the nodes are numbered using a 32-bit
integer.
>
>
> Can't Saxon use java.math.BigInteger instead of the 32-bit integer data
type? (if 32-bit integer constraint is not allowing Saxon to process
theoretically infinite size input stream).
>
>
>
>
> --
> Regards,
> Mukul Gandhi
> XSL-List info and archive
> EasyUnsubscribe (by email)
>
>
> XSL-List info and archive
> EasyUnsubscribe (by email)




--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
To avoid situations in which you might make mistakes may be the
biggest mistake of all
------------------------------------
Quality means doing it right when no one is looking.
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play
-------------------------------------
To achieve the impossible dream, try going to sleep.
-------------------------------------
Facts do not cease to exist because they are ignored.
-------------------------------------
Typing monkeys will write all Shakespeare's works in 200yrs.Will they
write all patents, too? :)
-------------------------------------
Sanity is madness put to good use.
-------------------------------------
I finally figured out the only reason to be alive is to enjoy it.

Current Thread