Eric Molitor wrote:
You are correct, the format is as follows.Command Packet * Header o length (4 bytes) o id (4 bytes) o flags (1 byte) o command set (1 byte) o command (1 byte) * data (Variable) Reply Packet * Header o length (4 bytes) o id (4 bytes) o flags (1 byte) o error code (2 bytes) * data (Variable) Source: http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jdwp-spec.html Also maybe useful: http://java.sun.com/j2se/1.5.0/docs/guide/jpda/socketTransport-example.c
Soooo, since they know the length it means they know the data to send, which means there is no valid excuse for not sending all the data at one time - ie in one call to the transport. Their use of TCP_NODELAY was simply a kludge, and a massive one at that.
I still think there are issues trying to map the byte-based RFC cwnds to a packet based cwnd in the stack, but the application is defintely broken.
rick jones - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
