Lists Home |
Date Index |
- From: "Matthew Sergeant (EML)" <Matthew.Sergeant@eml.ericsson.se>
- To: "'Nigel Byrnes'" <email@example.com>, firstname.lastname@example.org
- Date: Thu, 21 Jan 1999 10:19:57 +0100
> -----Original Message-----
> From: Nigel Byrnes [SMTP:email@example.com]
> Hi all
> We all know the benefits of representing "static" documents in XML. But
> considering where [HTML, VRML, etc] content is to be generated on the
> fly, as is frequently done by CGI scripts, is XML suitable for encoding
> the output data in these types of applications?
> Considering a simple hangman game, the application could either:
> 1. receive user-input and generate XML as output, which then has to be
> 2. receive user-input and generate format markup language-content as
> 3. another possibility?
Why not 1 and 2? That's what our web application here is doing. We
use XML because there has to be different levels of processing done on the
information stored in the XML. It's highly structured data, so we could have
chosen an object database, but i hate making purchase requests, and so XML
seemed like a good option. That and we needed to access the data from
different platforms and languages (Linux, NT, Perl, VBScript, Java).
I developed a solution that allows us to easily edit the XML in a
HTML form, and it automatically generates structured XML on the back end -
this XML is totally based on the form - there's no processing going on to
create structure when processing a form.
Currently these solutions are all in Perl, but they are implemented
on top of the raw expat API so they should convert easily to other
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)