-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Han,
Hanks Wang (hanwan) wrote: | But the question is, all these chunk and http header are in same frame | (get it from wireshark.). Then you need to increase the number of characters being sent. If you really are sending "something long" as a string, it's gonna fit into a single TCP frame. Consider sending more than, say, 1500 bytes or so. That should cross TCP frames. | Which means we need 3 frame for the case: the first frame will carry the | http header, the second will carry the first chunk data, the last frame | will carry the end chunk. This is never going to happen. Ignore TCP frame allocations because you can't control them. | Does it mean I need control the tcp/ip protocol? It's impossible, right? Pretty much. There are ways, but why would you want to? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfFcxgACgkQ9CaO5/Lv0PAWlgCeLFo/LtKMPCqTsOfRBXHvV3a4 N/EAn0AnTf+pVgmaEavRVGjVM9LzKpIo =Ip5i -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
