> Then what do you have after you remove the TCP headers at your > destination? NOTHING? Just because a protocol doesn't know the > internals of another protocol doesn't mean it would do anything about > it.
You seem to think headers are the only things in packets. After you remove a header you still have the payload. > BTW encapsulation and naive protocols are quite passe. Tell that to all OOP programmers in the world. They are all striving for encapsulation by using objects. > The most > optimized performance comes from smart implementations that break just > that rule. I agree 100%. Sure you can *implement* something with optimizations that break encapsulation but the TCP/IP specs strive for simplicity with encapsulation. Chris -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
