Hi, I'm fairly new to all things REST (and Web Services in general), but I do have some questions for you. Namely: - What do you think of the idea of having an...
... http://bitworking.org/news/193/Do-we-need-WADL ... We have one failed approach (with UDDI) already; not sure why we'd need another one. For enterprisey...
... Forms indeed are a key piece that needs to be looked at. I have found it inspiring to think of forms as questions available for the user agent to answer....
... Now that sound good. It's still an IDL isn't it ? It's just distributed directly by the service provider and is not exportable. But this and WADL are...
... Well, this makes a case against WADL, based on - experience with WSDL showing that people will want to generate code from it - the fact that current schema...
... Somewhat. AIUI, WADL is still a development-/compile-time description. Once you've written software to the described API, you're tightly coupled to that ...
Hi Henry, ... Thanks! I've added it to my REST Service Descriptions page: http://microformats.org/wiki/rest/description#Proposals.2FExamples Best, -- Ernie P....
Let's say we PUT some document to /articles/1. The document is XML, and has fields for a title, body, date, etc. The title is blank, but our app doesn't...
... Both 403 and 409 will work; you could also consider 422... In the end, I don't think it will matter unless you expect generic clients to do something with...
... Hash: SHA1 ... Pat> I'd really appreciate some insight into which code is the Pat> best to use. Of course if there's one more suitable than 403 Pat> and...
... What about 400? In the O'Reilly book, 'RESTful Web Services', they state for 400: "It's commonly used when the client submits a representation along with...
... 422 is in the IANA http status code registry, so it's not really different from any other status code, except that it's defined in a different document. ...
... Olivier, 1. signature!=interface. The original definition by D.L. Parnas defined interface as signature+semantics. In the absence of a formal language to...
Most(all?) of the REST theory I've read, and maybe all the examples, discusses altering the state of one resource when hitting a URL. But I keep bumping into...
... In my opinion, sometimes agreed to by others on this list and sometimes not, what the server does behind the scenes is the server's business. I can think...
Bob Haugen
bob.haugen@...
Aug 6, 2007 7:55 pm
9565
... That looks very much like the bank-transaction example in the REST book... if declaring a combination resource as Mike suggests doesn't cover it, or if you...
... Umm, all REST theory that I know about prevents you from knowing the extent to which one resource state is overlapped with other resources. In other...
is it overkill to have the browser POST/PUT to /.../a/ and then have the server send a 301 with the location of /.../b/? mca ... -- mca "In a time of universal...
... No, it’s not overkill, it’s just wrong. You’re telling the client that it should repeat the same POST/PUT against the resource at the redirected URI....
... I get this, but then I don't. I can see how this covers the case I gave in my example. But there are two possible generalizations which I can't quite make...
... I don't quite get this. Do you make a distinction between two resources whose state happens to have the same value, and two resources who share the same...
... Yeah, but there's no feature in REST that will let you know A and B will synchronise. That could be communicated over REST to something or someone that...
... will ... Well, maybe I have a synchronized clocks resource? /clocks/synchronized Which gets me back to my original problem, what is the best way to express...
Hello, ... I think it depends on whether-or-not resources A and B share state with another resource -- such as a database that supports transactions -- and on...
... Yes, using URI template syntax: http://example.com/color-combos/{color1}-and-{color2}/ ... Sure, if you need that. But I think maybe you should look at it...
... Oh, not at all. A resource is a thingy. Perfectly simple. GET the thingy, PUT the changed thingy, DELETE the thingy, POST a new thingy. The Internet is...