Cart
[Home] [By Thread] [By Date] [Recent Entries]
I'm working on my XML pipeline engine, Relay. I'm using special
URIs to view information as documents. I'm creating a servlet,
for example, that explodes the HttpServletRequest into a
document, so I can bite into it with XSLT.
<request>
<path-info>/foo/bar</path-info>
<server-name>engrm.com</server-name>
<content-type>application/x-www-form-urlencoded</content-type>
<content-uri>request://content/</content-uri>
</request>
The above document is available from the URI:
request://document/
As you can see, I get the input as a stream using:
request://content/
I parse the content of the post in a Relay, and it makes each
form field avaialable as a stream, in case one of the fields is
really a hidden field with an JavaScript generated XML document in it.
Or, else, I can run a textarea through HTML Tidy, to permit mild
markup in a comments box.
That URI looks like:
request://field/e-mail-address/1
Which will return the first field named e-mail-address as a
stream.
What do you all think? Am I designing these URIs correctly?
Should I bother making them heirarcical? Or should I simply
create my own interpreation of the scheme specific part?
request:document
request:content
request:field:e-mail-address[1]
Thanks.
--
Alan Gutierrez - alan@e...
- http://engrm.com/blogometer/index.html
- http://engrm.com/blogometer/rss.2.0.xml
|
