[Click] ARPTable element in wifi package?

[Eddie Kohler]

FWIW, I think elements like ARPTable fit the Click way of designing things 
perfectly well :)  It's an information element, like ScheduleInfo or 
IPRewriterPatterns.  In the particular case of ARPTable, it might be nice if 
ARPQuerier itself implemented ARPTable functionality, but I think the current 
design is AOK.

Eddie


John Bicket wrote:
> ARPTable is kind of a weird element - it doesn't process packets, 
> but just stores ip->ethernet mappings for other elements.
> 
> Most people really want ARPQuerier instead, and the only
> other code that uses ARPTable right now are elements for
> wireless routing.
> 
> I'm not really sure how to share data structures like ARPTable with other
> elements, and the easiest way was just to make ARPTable an element.
> But it's doesn't really fit with the click way of designing things.
> The same thing is true for the LinkTable element (it stores 
> link-state information for source routing).
> 
> --john
> 
> Jay Chen [j2chen at cs.ucsd.edu] wrote:
> 
>>Hi,
>>
>>I was just curious as to whether there was a special reason the ARPTable
>>element is in the wifi package?
>>
>>Thanks,
>>Jay
>>
>>_______________________________________________
>>click mailing list
>>click at amsterdam.lcs.mit.edu
>>https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> 
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click