On 29/06/07, Eric Lease Morgan <[log in to unmask]> wrote:
> Here are the only two working examples I have:
In terms of versioning and user readability (you never know someone
may want to bookmark a url :) ), you could perhaps try a url that
looked something like this using two examples above:
or even better...
which could lead to...
These urls can be interpreted by Mod Rewrite  rules to actually
present the name:value pairs to your perl app.
Of course this approach requires some planning - but in terms of
usability could have a payoff. If the api were only targeted at
developers and is only ever going to be embedded in code - never to be
seen by the masses - then name/value pairs may be ok.
In terms of xml output, I would echo Robert "i only have an opinion on
the nature of the xml to return, and only in the case of lists of
stuff: Atom or RSS. i'm really cursing myself for having fallen into
the trap of "hey, with xml i can create my own formats" too often."
Atom or RSS would allow greater mashupability - Yahoo Pipes etc.