Constructor Detail

• ConnectionDataReceiver

  public ConnectionDataReceiver(I2PAppContext ctx,
                                Connection con)

  Parameters:

  con - non-null

Method Detail

• destroy

  void destroy()

  Release resources held by this receiver.

• send

  public PacketLocal send(byte[] buf,
                          int off,
                          int size)

  Send some data through the connection, attaching any appropriate flags onto the packet. Called externally from Connection with args (null, 0, 0) to send an ack

  Parameters:

  buf - data to be sent - may be null

  off - offset into the buffer to start writing from

  size - how many bytes of the buffer to write (may be 0)

  Returns:

  the packet sent

• send

  public PacketLocal send(byte[] buf,
                          int off,
                          int size,
                          boolean forceIncrement)

  Called externally from Connection with args (null, 0, 0, true) to send an empty data packet

  Parameters:

  buf - data to be sent - may be null

  off - offset into the buffer to start writing from

  size - how many bytes of the buffer to write (may be 0)

  forceIncrement - even if the buffer is empty, increment the packetId so we get an ACK back

  Returns:

  the packet sent

• writeData

  public MessageOutputStream.WriteStatus writeData(byte[] buf,
                                                   int off,
                                                   int size)

  Send some data through the connection, or if there is no new data, this may generate a packet with a plain ACK/NACK or CLOSE, or nothing whatsoever if there's nothing new to send. This is called from MessageOutputStream, i.e. data from the client.

  Specified by:

  writeData in interface MessageOutputStream.DataReceiver

  Parameters:

  buf - data to be sent - may be null

  off - offset into the buffer to start writing from

  size - how many bytes of the buffer to write (may be 0)

  Returns:

  an object to allow optional blocking for data acceptance or delivery.

• writeInProcess

  public boolean writeInProcess()

  This tells the flusher in MessageOutputStream whether to flush. It won't flush if this returns true. It was: return con.getUnackedPacketsSent() > 0 (i.e. Nagle) But then, for data that fills more than one packet, the last part of the data isn't sent until all the previous packets are acked. Which is very slow. The poor interaction of Nagle and Delayed Acknowledgements is well-documented. So let's send data along unless the outbound window is full. (i.e. no-Nagle or TCP_NODELAY) Probably should have a configuration option for this.

  Specified by:

  writeInProcess in interface MessageOutputStream.DataReceiver

  Returns:

  !flush