wraggster
October 19th, 2005, 20:18
Source - http://www.drunkencoders.com/
sgstair:
I've been getting a lot of mail/etc from people suggesting that I use uIP to replace lwIP..... well, I'll briefly explain why I'm not doing that. First, have you seen uIP's interface? I mean, sure it has a small footprint but it looks like an utter pain to use for anyone but hardware engineers. Not to mention it doesn't support things we really like such as fragmented packet reordering, packet retransmission and other things people expect a TCP system to do. Were I to use uIP, I would basicly have to do the same amout of work I'm going to be doing with my own TCP stack, I still have to emulate sockets, and I would have to write most of the major features that a TCP system needs. Well, I don't mean to lash out at the people sending me links, as I'm glad people are interested and trying to help - but uIP just isn't going to cut it. We now return you to your regularly scheduled waiting...
http://www.akkit.org/dswifi/index.html
sgstair:
I've been getting a lot of mail/etc from people suggesting that I use uIP to replace lwIP..... well, I'll briefly explain why I'm not doing that. First, have you seen uIP's interface? I mean, sure it has a small footprint but it looks like an utter pain to use for anyone but hardware engineers. Not to mention it doesn't support things we really like such as fragmented packet reordering, packet retransmission and other things people expect a TCP system to do. Were I to use uIP, I would basicly have to do the same amout of work I'm going to be doing with my own TCP stack, I still have to emulate sockets, and I would have to write most of the major features that a TCP system needs. Well, I don't mean to lash out at the people sending me links, as I'm glad people are interested and trying to help - but uIP just isn't going to cut it. We now return you to your regularly scheduled waiting...
http://www.akkit.org/dswifi/index.html