| Time |
S |
Nick |
Message |
| 01:12 |
|
|
systmkor joined #rest |
| 02:37 |
|
|
tr3onlin_ joined #rest |
| 02:44 |
|
|
charlex_ joined #rest |
| 03:07 |
|
|
tmoore joined #rest |
| 03:11 |
|
|
bigbluehat_ joined #rest |
| 03:44 |
|
|
tr3online joined #rest |
| 03:50 |
|
|
rickharrison_ joined #rest |
| 04:37 |
|
|
systmkor joined #rest |
| 04:58 |
|
|
systmkor joined #rest |
| 05:10 |
|
|
trygvis_ joined #rest |
| 05:39 |
|
|
_ollie joined #rest |
| 06:41 |
|
|
rosstuck joined #rest |
| 07:15 |
|
|
Left_Turn joined #rest |
| 07:23 |
|
|
talios joined #rest |
| 07:54 |
|
|
tr3onlin_ joined #rest |
| 08:18 |
|
|
tr3online joined #rest |
| 10:25 |
|
|
shrink0r joined #rest |
| 10:34 |
|
|
_ollie joined #rest |
| 11:52 |
|
|
martinfilliau joined #rest |
| 12:05 |
|
|
charlex_ joined #rest |
| 12:25 |
|
|
_ollie joined #rest |
| 13:19 |
|
|
ironChic` joined #rest |
| 13:20 |
|
ironChic` |
in my application, i'm thinking of returning 300 Multiple Choices in response to POST requests |
| 13:20 |
|
pdurbin |
maybe it's time for pagination |
| 13:21 |
|
ironChic` |
the idea is that client sends partial information about a resource and the application responds by saying: based on that information, we can create either this, this, or this |
| 13:21 |
|
ironChic` |
does that sound at all sane? |
| 13:23 |
|
|
ironChicken joined #rest |
| 13:26 |
|
ironChicken |
the reason ironChic` and i (who are/is the same person) started worrying about this design was looking at this diagram: |
| 13:26 |
|
ironChicken |
https://raw.githubusercontent.com/wiki/basho/webmachine/images/http-headers-status-v3.png |
| 13:26 |
|
ironChicken |
which seems to imply that there's no route from POST to 300 |
| 13:32 |
|
|
charlex_ joined #rest |
| 13:42 |
|
|
Mxyzpltk joined #rest |
| 13:45 |
|
|
danizord joined #rest |
| 14:17 |
|
|
tr3online joined #rest |
| 14:33 |
|
fumanchu |
ironChicken: I see a route from POST to 300... |
| 14:34 |
|
ironChicken |
fumanchu: ok, that's reassuring |
| 14:34 |
|
ironChicken |
even if it does make me look a bit stupid ;-) |
| 14:35 |
|
fumanchu |
you must live in California, where all routes are straight and direct ;) |
| 14:36 |
|
* pdurbin |
is reminded of http://pdurbin.tumblr.com/post/41994788005 |
| 14:37 |
|
fumanchu |
:) |
| 14:40 |
|
ironChicken |
pdurbin: or https://maps.google.co.uk/?q=boston+lincolnshire or indeed any town in europe |
| 14:40 |
|
* fumanchu |
wants to take that webmachine graph and make it 3D so that the POST and PUT spiral down into a hell of misdirection, conflict and multiple choices |
| 14:41 |
|
ironChicken |
so does anyone see any obvious problems with responding 300 to POST requests? |
| 14:43 |
|
|
ironChic` left #rest |
| 14:46 |
|
fumanchu |
there's certainly no protocol problem. whether it's the appropriate solution for your problem is another question. typically, you return 300 because you ask for /foo and the server offers you /foo.jpg, /foo.pdf, /foo.html, etc. |
| 14:47 |
|
* fumanchu |
mixed up his "you's" there, but hopes it's clear |
| 14:47 |
|
ironChicken |
it is |
| 14:48 |
|
fumanchu |
see http://tools.ietf.org/html/rfc7231#section-3.4 |
| 14:51 |
|
ironChicken |
hmm. yeah. |
| 14:52 |
|
ironChicken |
i suppose what i'm doing is somewhat similar to RESTful search |
| 14:52 |
|
ironChicken |
except that the results list comprises things that will be created, rather than things that have been found |
| 15:05 |
|
Mxyzpltk |
what link relation should be used if a link points to a webpage with the profile of a person? |
| 15:07 |
|
|
pezra joined #rest |
| 15:35 |
|
|
danizord_ joined #rest |
| 15:51 |
|
|
charlex_ joined #rest |
| 16:18 |
|
|
pezra joined #rest |
| 16:59 |
|
|
tr3online joined #rest |
| 17:00 |
|
|
tr3online joined #rest |
| 17:14 |
|
|
pezra joined #rest |
| 17:26 |
|
trygvis_ |
Mxyzpltk: 'me' |
| 17:29 |
|
Mxyzpltk |
10x |
| 18:09 |
|
|
tr3online joined #rest |
| 18:25 |
|
|
cigarshark joined #rest |
| 18:38 |
|
|
systmkor joined #rest |
| 18:58 |
|
|
systmkor joined #rest |
| 20:53 |
|
|
tr3online joined #rest |
| 21:38 |
|
|
charlex_ joined #rest |
| 21:49 |
|
|
shrink0r joined #rest |
