So, take a look to current contrib repository. If we try to "define" these
applications characteristics, we have:
- chargen: socket api based, used only for tests, but can be used like this
(but since it's not used on any contrib buildable port, I'm not sure)
- netio: raw api based, used only for tests, but can be used like this
- httpserver: netconn api based, used for demo or need big changes to be
useful (no "dynamic" pages or cgi support)
- httpserver_raw: raw api based, used for demo or need big changes to be
useful (no "dynamic" pages or cgi support)
- netbios: raw api based, can be used with any target used on a "Windows"
LAN (perhaps same for linux?), but can be used like this (some @todo)
- ping: raw api based XOR socket api based, used only for tests or need
little changes to be useful (I will do this evening)
- sntp: socket api based, can be used like this.
Are you in favor to remove "chargen" and "sntp" ? I'm ok for "chargen", but
I think "sntp" could stay (I will perhaps add a raw api alternative).
On Wed, 2007-11-07 at 08:36 -0500, Pettinato, Jim wrote:
>I meant creating multiple directories in contrib/apps (e.g.
>contrib/apps/socket/, contrib/apps/netconn, contrib/apps/raw)
>and put the applications we already have in the right directory.
That's the decision that I thought we mutually arrived upon back when we
discussed restructuring... But I believe Kieran was holding off until
1.3.0 to restructure the repository?
I'd be fine with that. Might make things a bit easier than just having
them all in one directory, but even if that were the case we should
still have a little README with each app to say what it does, what API
it uses, who maintains it etc.
Kieran
_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel