[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
Re: [xml-dev] XML support in browsers?
- From: COUTHURES Alain <alain.couthures@agencexml.com>
- To: nico <ndebeiss@gmail.com>
- Date: Mon, 08 Jun 2009 11:24:31 +0200
Hello Nico,
> Concerning the lack of namespace axis support in firefox, there is a
> bug fixed : https://bugzilla.mozilla.org/show_bug.cgi?id=94270 but
> waiting to be loaded. The last problem is to say if the XSLT expression :
>
> <xsl:value-of
> select="string(count(nsa:data/descendant-or-self::*/namespace::*))"/>
>
> on that test :
>
> <nsa:testsuite
> xmlns:nsa="http://www.mozilla.org/firefox/xslt/namespace-axis">
> ...
> <nsa:test id="20">
> <nsa:assertion expectedvalue="3"
> uri="http://www.w3.org/TR/xpath#namespace-nodes">The
> 'nsa:data' element sub-tree has a total of 3 namespace
> nodes.</nsa:assertion>> <nsa:data>
> <x xmlns:edi="http://ecommerce.example.org/schema">
> <y/>
> </x>
> </nsa:data>
> </nsa:test>
> </nsa:testsuite>
>
> must return 3 nodes or 8 , but that is a minor problem I think.
I read that "3" is an XPath 1.0 answer while "8" is an XPath 2.0 answer,
is it correct ?
>
> There are still lots of performance issues triggering XSLT in the
> browser, and in firefox it freezes the whole navigation, which is
> difficult to accept. I think performance stays the major issue of XML
> against JSON, used on the client side.
XSLTForms (http://www.agencexml.com/xsltforms) is based on a rather
complex XSLT 1.0 transformation and the performance is very good indeed
(Javascript performance is problematic for big instances, not XSLT).
JSON support might be added to XSLTForms but it's another subject...
> Maybe we could trigger XSLT with options which reduce processing time,
> like disabling namespaces support, or using streaming capabilities.
Any global web client-side solution needs to run without plug-in or
options to trigger !!
Best regards,
Alain Couthures
<agenceXML>
Bordeaux, France
Twitter account: AlainCouthures
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]