| Time |
S |
Nick |
Message |
| 01:06 |
|
|
philbot joined #rest |
| 01:06 |
|
|
Topic for #rest is now #rest REpresentational State Transfer | logs: http://irclog.greptilian.com/rest/today | http://tech.groups.yahoo.com/group/rest-discuss | http://code.google.com/p/implementing-rest/ | http://en.wikipedia.org/wiki/Representational_State_Transfer |
| 08:20 |
|
|
Haudegen joined #rest |
| 09:30 |
|
|
wsieroci joined #rest |
| 10:08 |
|
|
interop_madness joined #rest |
| 10:21 |
|
|
kiero joined #rest |
| 10:28 |
|
kiero |
hi, do you recommend any book or guide for getting know everything about rest API (and not only this) for mobile developer? I mean how http works, http methods, api versioning, often used headers, authorizations, caching and so on? |
| 10:56 |
|
mdk |
kiero: "REST in practice" is nice even if they use a lot of XML |
| 12:31 |
|
|
Haudegen joined #rest |
| 18:04 |
|
|
linovia joined #rest |
| 18:04 |
|
linovia |
hi |
| 18:17 |
|
pdurbin |
hi linovia |
| 18:20 |
|
linovia |
There are a couple of things that are not cristal clear to me regarding the various constraints of the REST, in particular regarding some of Roy Fielding's comments |
| 18:20 |
|
linovia |
In particular, "all application state transitions must be driven by client selection of server-provided choices that are present in the received representations or implied by the user’s manipulation of those representations" |
| 18:21 |
|
linovia |
that means the representation should describe the next actions beside a simple link similar to html forms |
| 18:22 |
|
linovia |
but doesn't that contradicts a bit the separation from one entry point to another ? In particular if the said link belongs to a 3rd party API ? |
| 18:22 |
|
linovia |
and doesn't it also duplicate the content type too ? |
| 19:15 |
|
|
wsieroci joined #rest |
| 19:29 |
|
whartung |
no linovia |
| 19:30 |
|
whartung |
the idea is that the server presents the transition of application workflow and state through the links avallable in the hypermedia content. |
| 19:30 |
|
whartung |
(gah…and off I go to lunch..bbl) |
| 19:38 |
|
linovia |
well, I understand the last point of http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven as more than just the link |
| 19:39 |
|
linovia |
or you mean no to "doesn't it also duplicate the content type too" maybe |
| 20:50 |
|
whartung |
No, it doesn’t replace the content type, as the content type defines what the links are and how they’re used linovia |
| 22:05 |
|
linovia |
The thing I don't get is the third point at http://roy.gbiv.com/untangled/ |
| 22:07 |
|
linovia |
What I understand is that a representation should give hints about what's associated with an url. |
| 22:08 |
|
linovia |
This is similar to forms with HTML. But the content type should also describe what's expected from the server. |
| 22:11 |
|
linovia |
sorry, the previous link should have been http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven |
| 22:40 |
|
|
Haudegen joined #rest |
