TCP/IP

When using lwip, there is a number of main options:

1) No op.system

2) uc/OSII

3) uCLinux

4) RAW API

5) Socket API

If raw speed is the main priority, would be the fastest implementation? Or, is the speed differences more or less minimal?

Spec points:

----------------

- The application shall forwarding IP packets on a comms on power link. Reponses are routed back.

- The application shall have a Web server for configuration.

- The application shall be able to serve multiple TCP/IP connections, the typical number is max. 30. This implies that multi-threading would be "nice", but it can be solved even in a single-threaded environment of course.

- The application shall serve a serial port.

- Parts of the code shall be downloadable on the TCP/IP link (the system shall be split into a resident kernel and a downloadable application). Do any of the operating systems support this?

I can&#39;t simple make up my mind on which architecture to go for. Any input will be highly appreciated! Maybe the simplest would be to base everything on RAW api and no op.sys and evolve from here? http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/unsure.gif

I&#39;m just about to create an embeeded applicaiton that routes IP packets on