Time |
S |
Nick |
Message |
00:18 |
|
|
fuzzyhorns joined #rest |
00:41 |
|
|
baweaver joined #rest |
01:07 |
|
|
wsiqueir joined #rest |
02:01 |
|
|
mamund joined #rest |
03:18 |
|
|
fuzzyhorns joined #rest |
03:20 |
|
|
baweaver joined #rest |
07:06 |
|
|
_ollie joined #rest |
07:50 |
|
|
graste joined #rest |
09:05 |
|
|
quimrstorres joined #rest |
09:40 |
|
|
quimrstorres joined #rest |
10:09 |
|
|
quimrstorres joined #rest |
10:19 |
|
|
quimrstorres joined #rest |
10:34 |
|
|
rosstuck joined #rest |
10:42 |
|
|
quimrstorres joined #rest |
11:02 |
|
|
quimrstorres joined #rest |
11:05 |
|
|
quimrsto_ joined #rest |
12:44 |
|
|
ozette joined #rest |
13:13 |
|
|
quimrstorres joined #rest |
13:22 |
|
|
charginghawk joined #rest |
13:23 |
|
|
quimrstorres joined #rest |
13:26 |
|
charginghawk |
#rest, sorry to be asking this, but do you know a good channel for soap? |
13:29 |
|
* pdurbin |
thinks |
13:29 |
|
pdurbin |
charginghawk: are you using a particular library? |
13:32 |
|
charginghawk |
here's what I'm tangling with: http://help.sap.com/saphelpiis_cloud4hr/en/successfactors_hcm_suite_sfapi_handbook_en.pdf |
13:32 |
|
|
fuzzy_horns joined #rest |
13:33 |
|
charginghawk |
right now, I'm just trying to test it using clients like SoapUI or Web Service Studio |
14:11 |
|
|
Left_Turn joined #rest |
14:22 |
|
|
charginghawk joined #rest |
14:32 |
|
|
quimrstorres joined #rest |
14:33 |
|
pdurbin |
charginghawk: what language are you using? |
14:33 |
|
charginghawk |
php... *sob* |
14:34 |
|
pdurbin |
heh |
14:35 |
|
pdurbin |
charginghawk: sounds like your testing isn't going very well |
14:35 |
|
charginghawk |
not really |
14:36 |
|
|
ozette joined #rest |
14:37 |
|
|
cvander joined #rest |
14:39 |
|
pdurbin |
bummer |
14:54 |
|
ozette |
when talking about a POST request, what´s the alternative to query string parameters? |
14:55 |
|
ozette |
in a rest structure, you can have a POST to /login and then from a request object extract the username and password |
14:57 |
|
pdurbin |
ozette: well, you can put values in the path |
14:57 |
|
pdurbin |
or in headers |
14:59 |
|
ozette |
i once saw a piece of code which implemented a rest structure. the username and password were extracted from the request.body, like an object, but does a POST request have |
14:59 |
|
ozette |
an actual body? or was that just the header? |
15:00 |
|
fumanchu |
POST almost always has a body, yes |
15:00 |
|
pdurbin |
yeah. POST some JSON or whatever |
15:00 |
|
fumanchu |
of whatever Content-Type you like best |
15:02 |
|
sfisque |
if you really wanted, you could even do a multi-part, with the creds in one form stream, and the payload in the other form stream |
15:07 |
|
ozette |
ah |
15:14 |
|
ozette |
are request bodies is optional? because looking at a POST request i only see General, Response Headers, Request Headers and Query String Parameters |
15:16 |
|
ozette |
in my rest implementation, i want to be able to say something like request.body.key, so that means the client application would need to create a request body? |
15:22 |
|
fumanchu |
you'd have to ask in the channel for your server-side framework how to obtain and parse a request body |
15:26 |
|
|
ozette joined #rest |
15:39 |
|
|
fenjamin_ joined #rest |
15:39 |
|
sfisque |
at the raw level, the body follows the headers as a continuous stream (or series of streams in the case of multi-part). any decent web framework (as fumanchu indicates) will provide an api to extract and use the body of the request/response |
15:48 |
|
ozette |
thanks |
16:04 |
|
|
ozette joined #rest |
17:05 |
|
|
quimrstorres joined #rest |
17:17 |
|
|
charginghawk left #rest |
17:19 |
|
|
_ollie joined #rest |
17:32 |
|
|
_ollie joined #rest |
18:08 |
|
|
quimrstorres joined #rest |
18:43 |
|
|
fuzzyhorns joined #rest |
18:54 |
|
|
baweaver joined #rest |
20:59 |
|
|
blahdeblah joined #rest |
21:29 |
|
|
quimrstorres joined #rest |
22:31 |
|
|
quimrstorres joined #rest |
22:52 |
|
|
verumequals joined #rest |
23:03 |
|
|
Mxyzpltk joined #rest |
23:41 |
|
|
sfisque joined #rest |