RFC : XML representation of a HTTP request

Eric van der Vlist vdv at dyomedea.com
Fri Jan 21 07:30:38 GMT 2000


In a java servlet environment, I have developed a mapping of the HTTP
request into a result tree fragment through sax events and I'd like to
have your feedback on the structure I am proposing.

Currently, this structure is something which, translated into XML, would
be like :


(It could be extended to the cookies as well.)

The names of the headers, variables or parameters is used as the name of
the entities.

The path to the variable "URI" is therefore : "/request/variables/URI".

Would it be better to have a common entity name and something like :

       <parameter name="x">2</parameter>

The path to the variable "URI" would then be  :

If it's the case and if we have different entity names for the
parameters, headers, variables (and later on cookies), do we need to
keep a structured path to these different entities since a path of 
"/request/variable[@name='URI']" would already be sufficient to
differentiate the variable "URI" from a possible parameter "URI" ?

And of course, If I am reinventing the wheel and if a XML schema to
represent a request context has already been defined, I'll be very glad
to know it !

Related links :

	(the example with its code)

	(newly created discussion list for these "tips")

Thanks for your feedback.


Eric van der Vlist                                              Dyomedea

http://www.dyomedea.com                          http://www.ducotede.com

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Unsubscribe by posting to majordom at ic.ac.uk the message
unsubscribe xml-dev  (or)
unsubscribe xml-dev your-subscribed-email at your-subscribed-address

Please note: New list subscriptions now closed in preparation for transfer to OASIS.

More information about the Xml-dev mailing list