lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] coap on lwip


From: chrysn
Subject: Re: [lwip-users] coap on lwip
Date: Fri, 18 Jan 2013 16:26:12 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Jan 17, 2013 at 11:45:43PM +0100, chrysn wrote:
> i've created an initial port and uploaded it to a dedicated project on
> gitorious[1].

i should have added that this is supposed to work with the 1.4.1 stable
version of lwip.

while looking at which branch to base the doxygen work on, i saw that
much of the address handling changed, looks like preparations for the
1.5 dualstack operation.

as the address support in the lwip coap poart is very hackish for now,
i'm facing the decision whether to stay compatible to 1.4 or to ditch it
and use the new shiny 1.5 addresses. in other words:

* how far is lwip in the 1.5 release process? are we talking weeks,
  months or years?

* will there be address copying and comparison operations in 1.5? (or
  are there even any in 1.4?)

  (for now, in the coap headers i define a
  
      #define _coap_address_equals_impl(A, B) ((A)->addr.addr == (B)->addr.addr 
&& A->port == B->port)

  for coap's address struct

      typedef struct __coap_address_t {
        uint16_t port;
        ip_addr_t addr;
      } __coap_address_t;

  and i copy them over with b.addr = a.addr, but at least with a
  powerful address struct, this will have to change.)

* competely unrelated: i'm working from a git checkout, and have never
  used cvs. is there anything i should take care of when adapting things
  for doxygen builds?

best regards
chrysn

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]