Gents,
to sum it up, arguments made and details of how I see the
implementation of a response/request encode/decode framework:
* need a pluggable interface so current content-types are supported
(`application/x-www-form-urlencoded`, `multipart/form-data`), new
types (`application/json`), custom an
On Tue, Sep 10, 2013 at 9:05 AM, Curtis Maloney
wrote:
>
> On 9 September 2013 19:50, S Berder wrote:
>>
>> Gents,
>> to sum it up, arguments made and details of how I see the
>> implementation of a response/request encode/decode framework:
>>
>> * nee
On Tue, Sep 10, 2013 at 12:17 PM, S Berder wrote:
> On Tue, Sep 10, 2013 at 9:05 AM, Curtis Maloney
> wrote:
>>
>> On 9 September 2013 19:50, S Berder wrote:
>>>
>>> Gents,
>>> to sum it up, arguments made and details of how I see the
>>&
> progress. (And perhaps collaborate.)
>
> Cheers :)
>
> Tom
>
> On Wednesday, 11 September 2013 04:52:08 UTC+1, Stefan Berder wrote:
>>
>> On Tue, Sep 10, 2013 at 12:17 PM, S Berder wrote:
>> > On Tue, Sep 10, 2013 at 9:05 AM, Curtis Malone