[net2-wg] Packet interface

[Omprakash Gnawali]

> > It's definitely the case that an app can have N entries, if it wants.  
> > There's no restriction in that regard. Chances are a pool entry is  
> > ~20 bytes at most.
> 
> Cool, but can an app decide at runtime that it wants to send to N+1
> sources instead of N?  Mightn't that be useful at some point in the
> long-lived future of TOS-2?
> 
> Kyle


Is the expected usage pattern of SendPoolEntry a set of communication
state/handles that might be active concurrently and can be reused for
differnt destinations at different times ? In that case, if an
application wants to communicate to N+1 sources, but not at the same
time, then we can have the application reuse a SendPoolEntry depending
on the time, protocol etc. So, practically, declaring a handful of
entries will take care of most cases if you keep track of which
Entries are no longer in use much like message pool management.

But as Kyle said, it is not obvious how an application would increase
the number of entries on the fly (if N is a large number). If this
feature is necessary, some sort of allocation / deallocation of
Entries ? Sounds like an overkill though.