Hello,
I'm a low level networking programmer at HP. We are currently investigating network stacks to replace our current stack (VxWorks by WindRiver). I found lwip stack and it looks promising. I am currently familiarizing myself with the raw api.
I wanted to introduce myself and get a feel for the state of the project.
I did have a question about the raw api as I was reading. I thought it was odd that the tcp_listen call essentially re-allocated the tcp data structure since the listener didn't need as much memory. It would seem to me that the ideal api would provide a way for the application to create a "listener-specific" tcp data structure when it is created (instead of waiting for the listen call).
My guess is this was a hiccup brought in from the BSD socket api. Creating a function like tcp_new_listener() would allow new applications to use the simpler interface, and allow older applications to use the current api. Are these thoughts valid or is there a reason for this that I'm missing?
Thanks in advance for any response. This stack seems very promising. If we decide it is sufficient it will be utilized by a few dozen programmers on our enterprise printers.