httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe+gm...@sunstarsys.com>
Subject Re: [PATCH] Basic apr_xml_parser
Date Mon, 06 Sep 2004 17:42:16 GMT
Markus Wichitill <mawic@gmx.de> writes:

> Hm, is this going to hold back a stable release, or is it more of a
> side project? Just wondering, because a few weeks ago no common
> browser supported XForms

Having an XML parser included is necessary for XForms, but not
sufficient.  The mfd & url parsers would also need to become 
XForms-aware.

However there are plenty of non-XForms applications (DAV, SOAP, XMLRPC)
that could benefit from having an xml-aware libapreq2.  It's not a
side project.  The only thing that would hold up a stable release
is a lack of certainty about our existing APIs.  We can always add
new APIs after releasing a stable version- but we would not be 
able to change our existing APIs.

> and no browser developer had any plans to support them in the
> future. 

Personally I don't consider the "Microsoft standard" to be a
reasonable basis for deciding what things to include in libapreq.
There are already over two dozen implementations of XForms on the 
client-side, including various IE6 plugins.  On the server-side,
Cocoon already implements it.  Why shouldn't we?

-- 
Joe Schaefer


Mime
View raw message