> Yikes!  Well I'd just like to say what an absolutely amazing job you're
> doing, and a huge thank you.  Every web page that our company serves up
goes
> through Xalan (and has done for around two years now).  If you ever find
> yourself in the original Cambridge, then you're most welcome to look me
up
> for as many well deserved warm, flat alcoholic beverages as you can
stomach.

Thanks, it's nice to know when and how people are using the software, and
they appreciate it! ;-)  I'm actually not living and/or working in
Cambridge any longer, (I'm in sunny Californai), but I'll certainly take
you up on your offer should I find myself in the UK again.  (Who knows, it
might happen...)

> On that score, I've just finished persuading the co. to release the code
to
> what we use under LGPL -- essentially it's an ISAPI extension that makes
> asynchronous HTTP requests for the documents, stylesheets and any
includes
> in either (essential as IIS will lockup if you make synchronous
requests).
> That allows you to generate the XML document via ASP (or otherwise),
which
> makes the whole thing pretty dynamic.  In addition (with some fiddling),
> each included XML document can be treated separately wrt to POST data,
which
> allows you to build forms from collections of separate XML documents (we
> call those templates, to be slightly confusing), and POST to them all at
> once, without their knowledge.  Hmm, that's not explained very well :)
It
> lets you do some interesting things anyway!

Sounds very interesting -- you'll probably find others are looking for just
that sort of thing.  Are you going to release it on the company's web site,
or through something like SourceForge?

> No worries wrt to the patches, I figured you were busy.  If you want to
get
> the basic URI fixes in for 1.5, the code that I have shouldn't break
> anything (unless it relies on the bug), so that could be dropped in (old
> behaviour wrt to file:// and flip slashes is retained).  I've got a test
app
> for it as well, which shows that at least it conforms to the examples
given
> in the RFC.

We should definitely go into more detail regarding your previous email
about URISupport.  There's actually a good reason why "\" is always
normalized to "/", but I can go into more detail when I get back to your
previous message. (hint: take a look the document() function in XSLT.)
When I get some time in the next couple of days, I'll take a look at the
patch and see what happens when I apply it.

Thanks again!

Dave

Reply via email to