On Wed, 06 Sep 2006 18:29:35 +0200, Mark Baker <[EMAIL PROTECTED]> wrote:
I don't really see what you mean with the efficiency argument
I mean that I want to be able to hand off the incoming data stream to
the correct processor at the earliest possible time to minimize
latency, and since the media type arrives before the root namespace -
and in plain text form (not encrypted or compressed) - it's more
efficient to do so using its value.
Since it has to go through an XML parser regardless (at which point you
can easily make that check) I don't see the point.
and the
security argument applies nonetheless given that you also want to
support
it for arbitrary XML media types.
I'm not sure what security issue you're referring to, but I'm
referring to the kind that results from sniffing where documents can
be crafted which can masquerade for other formats, bypassing firewall
policies.
There's also the issue of placing unnecessary constraints on XML
language designers. The namespace of the root element isn't special,
and I should be allowed to design an XML format which has a root
element with any namespace. Like RDF/XML or XSLT, as mentioned
before.
This isn't really an issue for XBL. The format expected when it's
retrieved is XBL and if it's not it will simply yield in an error.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
