Eric Scheid wrote:
What I mean is that some servers will be implemented using one code base,
and other servers different code bases. Some will expect URL arguments in
this form:
http://example.com/feed.cgi?a=1&b=2&c=3
while another looks like this
http://example.com/cgi-bin/foo?a:1;b:2;c:3
I'm not sure I get it. Are you saying that there are some systems out there
that aren't capable of processing HTTP queries unless they're formatted in a
specific way? That's pretty frightening. I've never come across anything
like that before.
Is this an issue with a particular language? operating system? web server
architecture? I'm just curious.
We don't legislate that atom feeds end with .atom, allowing feed.php,
feed.xml, etc; so why should we legislate the form of app:seek?
Well we do legislate that an atom feed is XML, that it's an Atom document,
etc. There's a limit to how much flexibility can/should be provided.
However, if you say there's a need for templated URLs I'll take your word
for it.
Regards
James
