greptilian logo

IRC log for #rest, 2014-07-10

https://trygvis.io/rest-wiki/

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
02:07 philbot joined #rest
02:07 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
02:39 wilmoore joined #rest
06:48 _ollie joined #rest
06:48 _ollie joined #rest
06:59 rosstuck joined #rest
07:16 danielemm joined #rest
09:00 martinfilliau joined #rest
09:09 rosstuck joined #rest
09:57 DrCode joined #rest
10:04 fumanchu joined #rest
10:04 graste joined #rest
10:15 DrCode joined #rest
10:39 rosstuck joined #rest
11:14 pdurbin joined #rest
12:48 charlie_ joined #rest
13:01 danizord joined #rest
13:42 _ollie joined #rest
14:41 KarlHungus joined #rest
14:54 martinfi_ joined #rest
15:37 rosstuck joined #rest
15:59 martinfilliau joined #rest
16:59 wilmoore joined #rest
18:10 danizord joined #rest
18:46 wilmoore joined #rest
18:56 pezra joined #rest
19:07 wabash joined #rest
19:07 wabash hey folks
19:07 wabash how is everyone? I have some questions about Rest and rest testing.
19:07 wabash First question about REST.    PUT vs. POST. Is it a corrrect understanding to say that we should use PUT for things that are idempotent whenever we can, and POST for things that are not idempotent?
19:08 _ollie that's not a should actually, that's a must :)
19:08 wabash Right!
19:08 wabash _ollie: But, is this the correct relationship? Most people think interms of POST:create, PUT:update. Which I think is wrong.
19:09 _ollie well, that assignment is a consequence of the definition… plus, you can't map every interaction with a resource to create or put…
19:09 wabash I agree.
19:09 _ollie what about assignments, etc.
19:09 wabash So, the differentiating factor between POST and PUT is idempotency, correct?
19:10 _ollie yes… PUT has more guarantees
19:10 _ollie you can retry if you failed
19:10 wabash Is it summed up completely by idempotency? or is that only partial.
19:10 _ollie you might be able to with POST but that's not guaranteed
19:11 graste joined #rest
19:11 _ollie http://stackoverflow.com/questions/630453/put-vs-post-in-rest
19:11 wabash _ollie: Thanks. I want to make sure I'm understanding this correctly though.  does idempotency fully describe their differences? or is it missing some other aspects too
19:13 wabash _ollie: Am I missing something?
19:16 wabash I've lost you then.
19:16 wabash let me know when you are available.
20:02 wabash Ok, anyone else willing to discuss REST with me?
20:05 wabash Does anyone here use SoapUI?
20:06 whartung what do you need wabash
20:07 wabash whartung: Well, first, I'd like to ask for suggestions/recommendations for testing REST services.
20:07 whartung I'm not the person to ask that :)
20:08 wabash hahaha
20:08 whartung my testing is limited to random curl commands
20:08 wilmoore joined #rest
20:08 wabash whartung: Then, I'd like to make sure I'm understanding PUT vs POST. It seems to me right now that the differentiating factor is that of idempotency:   PUT for idempotent, POST for non-idempotent.  Makes sense, but I want to make sure I'm not missing a subtle detail.
20:09 whartung POST is kind of a catchall, the semantics around PUT are more formal
20:09 wabash tell me more
20:10 whartung PUT is like assignment. PUT basically "sets" the resource via a representation.
20:11 wabash yes
20:11 wabash But what's teh differentiating factor?
20:11 whartung POST is more wild west.
20:11 whartung basically you have GET, PUT, DELETE…and POST for "everything else"
20:12 whartung GET, PUT, DELETE are more primitves. POST can do "anything"
20:13 whartung G/P/D have implied semantics (notably for caching and proxies), POST just burns through all that. it doesn't have really any semanctics, so middlewear can't make any assumptions about POST requests
20:13 wabash whartung: So idempotency is just *one* semantic implication for PUT. correct?
20:14 whartung yes, but it's the one that middleware would consider the most.
20:15 wabash I agree.
20:15 wabash what are some of the other implied semantics?
20:19 whartung just the fact that PUT set the value, so PUT can invalidate caches and such.
22:03 wabash left #rest
22:33 daxim joined #rest
22:33 blongden joined #rest
22:33 riddle joined #rest
22:36 bigbluehat joined #rest
22:36 rickharrison joined #rest
22:36 tmoore joined #rest
22:36 ChrisAnn joined #rest
22:36 locks joined #rest
22:36 jgornick joined #rest
22:36 gamache joined #rest

| Channels | #rest index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

https://trygvis.io/rest-wiki/