Re: [xsl] [ANN] Saxon-CE - XSLT 2.0 on the browser

Subject: Re: [xsl] [ANN] Saxon-CE - XSLT 2.0 on the browser
From: Manfred Staudinger <manfred.staudinger@xxxxxxxxx>
Date: Mon, 28 Mar 2011 19:41:44 +0200
Well, to be cllear, in my case _all_ the user-agents get the same
source - it's their part to interpret.

Regards,
Manfred

On 28/03/2011, Michael Dykman <mdykman@xxxxxxxxx> wrote:
> I have a framework of my own design which relies very heavily on XSL
> 1.0 in the browser.  It employs user-agent introspection to determine
> if the requesting browser is capable of performing an XSL transform
> (for xsl 1.0, all modern browsers are compliant enough) and unknown
> browsers get rendered on the server-side.  That includes google and
> bing robots not to mention any lynx or curl calls that come my way.
>
> My partners and I have been building ever-more ambitious applications
> on this platform for nearly 3 years.
>
>  - michael dykman
>
>
> On Mon, Mar 28, 2011 at 1:25 PM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
>> On 28/03/2011 17:31, Dimitre Novatchev wrote:
>>>
>>> How would search engines find data?
>>
>> I'm not sure I know the answer, but I don't think the situation is any
>> different from the case where the content fetched from the server is
>> manipulated by client-side Javascript. In fact, it's identical, because
>> the
>> XSLT processor is implemented in client-side Javascript.
>>
>> Michael Kay
>> Saxonica
>>
>>
>
>
>
> --
>  - michael dykman
>  - mdykman@xxxxxxxxx
>
>  May the Source be with you.

Current Thread