Anticipating application initialization code like this:
<wait on semaphore signaled by a NET_DHCP_IPV4_ADDR_ACQUIRED callback >
<use pre-configured static ip address>
It probably doesn't matter how the address is acquired, but the
application needs to somehow know to wait for the IPv4 address
notification before proceeding. If DHCPV4 is configured, at least
the app knows it needs to wait in that case.
Could also remove the #ifdef in the app, have the app ask the net
interface if DHCP is supported (or if IP to be assigned by other
means), and if so, register to wait on a semaphore and wait on it,
otherwise proceed with a static IP address.
On 23 February 2017 at 12:49, Marcus Shawcroft
On 23 February 2017 at 19:35, Gil Pitney <firstname.lastname@example.org> wrote:HiIn the existing DHCP design it’s not enough for application just subscribe+1.