On Wednesday 13 June 2007 01:54, Vincent Trouilliez wrote: > reasonable overview of the background concepts, along with some idea > of what a practical implementation looks like, and then they should > be clever/responsible enough to understand that I can't possibly be > expected to learn 5,000 pages of RFC's by heart (and I bet none of > the engineers who implemented TCP/IP in their current products, do > either ! ;-), but that I rather need to actually work on their > products to train myself on the particular bits of the protocol that > they actually need/use in their products. > > Thanks again guys, I know what to do now...
If it was me I'd be looking at reusing an existing implementation, eg uIP-AVR -> http://www.laskater.com/projects/uipAVRdownload.htm It's 3 clause BSD licensed so you can probably use it at work with minimal problems. I'm all for not re-inventing the wheel... Especially hideously complicated wheels like TCP with fiddly corner cases :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
pgpCiOcBbHNVB.pgp
Description: PGP signature
_______________________________________________ AVR-chat mailing list AVR-chat@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-chat