[Seaside] Seaside-REST, PUT, and the Server adaptors
Philippe Marschall
philippe.marschall at gmail.com
Fri Apr 15 07:40:50 UTC 2011
2011/4/14 Tobias Pape <Das.Linux at gmx.de>:
>
> Am 2011-04-14 um 18:40 schrieb Philippe Marschall:
>
>> 2011/4/5 Tobias Pape <Das.Linux at gmx.de>:
>>> Dear all
>>>
>>> I played around with the Seaside-REST-portion for SqueakSource3
>>> by Phillippe, and I figured, that it depends (at least for Squeak/Pharo)
>>> on the Adaptor whether it is possible to use PUT-Requests or not:
>>>
>>> Having this code:
>>> putMap: fileName ofProject: projectName
>>> <PUT>
>>> <Path: '/{projectName}/{fileName}.mcm'>
>>> | data |
>>> data := self requestContext request rawBody.
>>>
>>> When using the Swazoo-Adaptor, data is nil, whatever I try
>>> (certain combinations of raw sending, url-encode, form-encode
>>> and the like)
>>
>> Do you have a dump of the request? Do you have an easy way to
>> reproduce it (Pharo 1.1 doesn't seem to ship with mcm)? I tried
>> something very simple and could not reproduce it immediately.
>
> Dump at the end
> the point isn't the mcm but the rawBody being nil when Using
> Swazoo.
>
> So any
>
> putSomething: fileName
> <PUT>
> <Path: '/fileName'>
> | data |
> data := self requestContext request rawBody.
>
> shall result in data being nil.
> ( I verified in the Seaside OneClick)
>
> put was done using:
> curl -v -X PUT -T Seaside-GemStone-REST-Core-topa.2.mcz http://localhost:8888/rest/
Thanks, I'll try that. Can you tell me which version of Swazoo you use?
Cheers
Philippe
More information about the seaside
mailing list