On Sun, 20 Feb 2011 22:32:47 +0100, Angelo P. Castellani wrote:
> The correct link follows:
> https://telecom.dei.unipd.it/tlcrepos/castellani/iot/coap-proxy
>
> Best,
> Angelo
>
Greetings.
You may find it more worthwhile to track as a branch off our "trunk"
code. HTTP/1.1 support is much more complete there.
I've had a look at the IETF drafts you linked. But not able to access
SVN yet.
Do you have any ideas why CoAP is better than chunked-encoded or Range
requests? or is that a CoAP to HTTP ranges gateway you are implementing?
Amos
> On Sun, Feb 20, 2011 at 22:22, Angelo P. Castellani wrote:
>> Dear squid developers,
>>
>> in an internal project we are working on the implementation of CoAP
>> on
>> constrained devices.
>>
>> For more informations about CoAP look at the IETF CoRE WG:
>> https://datatracker.ietf.org/wg/core/
>>
>> We have recently started investigating the development of an
>> HTTP/CoAP
>> mapping proxy based on squid.
>>
>> The modified version of squid-3.1.9 is available on the following
>> SVN
>> repository:
>> http://telecom.dei.unipd.it/tlcrepos/castellani/iot/coap-proxy
>>
>> user: guest
>> password: guest
>>
>> Please take in mind that the early stage of this implementation and
>> the fact that we are new to the squid codebase make this work hardly
>> usable.
>>
>> Right now its scope is limited to investigate the feasibility of
>> this approach.
>>
>> Any kind of feedback is welcome.
>>
>> Best regards,
>> Angelo P. Castellani
>>
Received on Sun Feb 20 2011 - 23:03:32 MST
This archive was generated by hypermail 2.2.0 : Mon Feb 21 2011 - 12:00:04 MST