On Dec 18, 2014, at 2:53 AM, Renat Akhmerov rakhme...@mirantis.com wrote:
Doug,
Sorry for trying to resurrect this thread again. It seems to be pretty
important for us. Do you have some comments on that? Or if you need more
context please also let us know.
WSME has separate handlers for
Ok, Doug, we’ll look into it.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 18 Dec 2014, at 22:59, Doug Hellmann d...@doughellmann.com wrote:
On Dec 18, 2014, at 2:53 AM, Renat Akhmerov rakhme...@mirantis.com
mailto:rakhme...@mirantis.com wrote:
Doug,
Sorry for trying to resurrect
Doug,
Sorry for trying to resurrect this thread again. It seems to be pretty
important for us. Do you have some comments on that? Or if you need more
context please also let us know.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 27 Nov 2014, at 17:43, Renat Akhmerov rakhme...@mirantis.com
Doug, thanks for your answer!
My explanations below..
On 26 Nov 2014, at 21:18, Doug Hellmann d...@doughellmann.com wrote:
On Nov 26, 2014, at 3:49 AM, Renat Akhmerov rakhme...@mirantis.com
mailto:rakhme...@mirantis.com wrote:
Hi,
I traced the WSME code and found a place [0]
Hi,
I traced the WSME code and found a place [0] where it tries to get arguments
from request body based on different mimetype. So looks like WSME supports only
json, xml and “application/x-www-form-urlencoded”.
So my question is: Can we fix WSME to also support “text/plain” mimetype? I
think
On Nov 26, 2014, at 3:49 AM, Renat Akhmerov rakhme...@mirantis.com wrote:
Hi,
I traced the WSME code and found a place [0] where it tries to get arguments
from request body based on different mimetype. So looks like WSME supports
only json, xml and “application/x-www-form-urlencoded”.
Hi, folks!
I try to create a controller which should receive one http content-type in
request but it should be another content-type in response. I tried to use
pecan and wsme decorators for controller's methods.
I just want to receive text on server and send json-encoded string from
server
