Ajith Ranabahu wrote:
Hi,
my understanding is that we support file handling in terms of MTOM/XOP
where the file content (presumed binary) goes on as
part of the payload. In terms of pure SOAP processing I don't think
there is anything described with HTTP PUT so looking at Axis2/C as a
SOAP processor I don't see where the PUT support fits in.
Agreed.
if there is a need to support PUT as part of REST my guess is we need
to discuss a bit more of where exactly we need PUT to be. The
semantics of PUT is to 'store' something in the server and IMHO our
current service model does not have such a semantic [either in REST or
SOAP]. The semantic we have right now is a file as an input to a
service (if there is file argument somewhere) and that IMHO should be
sent in some format in a POST (may be multipart/form-data ?)
Well can we not leave the semntics of "store" to the service
implementer? As the engine, what we are interested in is, if it is a PUT
request, locate the operation that maps to it and pass on the payload.
Then as far as the engine is concerned we are done. The semantics on
what to do in within the operation that maps to a PUT is up to the user.
IMHO, if we try and deal with the REST PUT semantics at the engine
level, we are making things overly complicated.
Thanks,
Samisa...
In any case we need a clear discussion on how ,what and where PUT
(and DELETE) should be placed in Axis2.
Ajith
On Jan 28, 2008 12:56 PM, Senaka Fernando <[EMAIL PROTECTED]> wrote:
Hi again,
I managed to tweak this on CURL. Instead of using,
curl_easy_setopt(handler, CURLOPT_PUT, 1) I used curl_easy_setopt(handler,
CURLOPT_CUSTOMREQUEST, "PUT"). However, how should we be placed in
supporting sending files using PUT?
Thanks,
Senaka
Hi Devs,
The traditional use-case of a PUT is to upload a file. And, in CURL, it is
asking for a file_pointer instead of a character stream.
Are we using PUT to send XML data? or files?
If we send files, how are we going to handle them?
If we wont send files, what about PUT on curl?
Regards,
Senaka
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
