On Fri, 2011-06-03 at 10:24 +0200, Michal Fojtik wrote: > On Jun 2, 2011, at 10:00 PM, Tomas Von Veschler wrote: > > Hi guys, > > I was thinking about this issue and how to handle it in proper 'REST-way' > (tm). > I asked on different channels and I got this idea: > > OPTIONS /api/instances/(constrains|params)/name > > This will return an XML/JSON with 'name' definition, validation and > requirements, > something that David proposed.
That seems overkill to me - why would we force clients to make one request per parameter ? I think describing it in the /api XML should be enough. I was actually thinking in the other direction, that we should put more of the /api XML into the response from /api/drivers so that clients can get an overview of what's supported by all the drivers on a given server. I am open to also expand what we send back for OPTIONS /api/:collection/:operation to be more descriptive, but I'd first like to hear from users if that would be useful to them. David
