- To: "Dare Obasanjo" <dareo@m...>,"Elliotte Harold" <elharo@m...>
- Subject: RE: Partyin' like it's 1999
- From: "Joshua Allen" <joshuaa@m...>
- Date: Wed, 27 Oct 2004 07:58:07 -0700
- Cc: <xml-dev@l...>
- Thread-index: AcS8Ik8/PgKdH7WET3muE05gfh9EyAAEeJGFAAA/4AA=
- Thread-topic: Partyin' like it's 1999
Title: Re: Partyin' like it's 1999
This was the same old, “screw the
users, screw perf, shove everyone into lowest common denominator and reduce
options because users are idiots who shouldn’t have choices” post.
From: Dare Obasanjo
Sent: Wednesday, October 27, 2004
7:56 AM
To: Elliotte Harold; Joshua Allen
Cc: xml-dev@l...
Subject: RE: Partyin'
like it's 1999
The fact that namespaces in XML requires
you to parse all attributes before you can report the name of the start tag
even in streaming implementations adds a significant perf cost. I'm not even
sure what the heck you mean by "complexity of allowing streaming
attributes" considering that whatever API does this is already streaming
everything else which makes not streaming attributes an inconsistency anyway.
If you don't change your direction, you may end up where you
were headed.
From: Elliotte Harold
[mailto:elharo@m...]
Sent: Wed 10/27/2004 5:09 AM
To: Joshua Allen
Cc: xml-dev@l...
Subject: Re: Partyin'
like it's 1999
This
doesn't arise in practice. It's a corner case. Tool vendors need to
handle it, but honestly the API complexity of allowing streaming
attributes argues against this approach, even if it were possible to
implement.
|
|
Cart
