Fields Summary |
---|
public static final int | ASCII_MODEThe ascii transfer mode. Its value is 0 and equivalent to NETASCII_MODE |
public static final int | NETASCII_MODEThe netascii transfer mode. Its value is 0. |
public static final int | BINARY_MODEThe binary transfer mode. Its value is 1 and equivalent to OCTET_MODE. |
public static final int | IMAGE_MODEThe image transfer mode. Its value is 1 and equivalent to OCTET_MODE. |
public static final int | OCTET_MODEThe octet transfer mode. Its value is 1. |
public static final int | DEFAULT_TIMEOUTThe default number of milliseconds to wait to receive a datagram
before timing out. The default is 5000 milliseconds (5 seconds). |
public static final int | DEFAULT_PORTThe default TFTP port according to RFC 783 is 69. |
static final int | PACKET_SIZEThe size to use for TFTP packet buffers. Its 4 plus the
TFTPPacket.SEGMENT_SIZE, i.e. 516. |
private byte[] | __receiveBufferA buffer used to accelerate receives in bufferedReceive() |
private DatagramPacket | __receiveDatagramA datagram used to minimize memory allocation in bufferedReceive() |
private DatagramPacket | __sendDatagramA datagram used to minimize memory allocation in bufferedSend() |
byte[] | _sendBufferA buffer used to accelerate sends in bufferedSend().
It is left package visible so that TFTPClient may be slightly more
efficient during file sends. It saves the creation of an
additional buffer and prevents a buffer copy in _newDataPcket(). |
Methods Summary |
---|
public final void | beginBufferedOps()Initializes the internal buffers. Buffers are used by
{@link #bufferedSend bufferedSend() } and
{@link #bufferedReceive bufferedReceive() }. This
method must be called before calling either one of those two
methods. When you finish using buffered operations, you must
call {@link #endBufferedOps endBufferedOps() }.
__receiveBuffer = new byte[PACKET_SIZE];
__receiveDatagram =
new DatagramPacket(__receiveBuffer, __receiveBuffer.length);
_sendBuffer = new byte[PACKET_SIZE];
__sendDatagram =
new DatagramPacket(_sendBuffer, _sendBuffer.length);
|
public final TFTPPacket | bufferedReceive()This is a special method to perform a more efficient packet receive.
It should only be used after calling
{@link #beginBufferedOps beginBufferedOps() }. beginBufferedOps()
initializes a set of buffers used internally that prevent the new
allocation of a DatagramPacket and byte array for each send and receive.
To use these buffers you must call the bufferedReceive() and
bufferedSend() methods instead of send() and receive(). You must
also be certain that you don't manipulate the resulting packet in
such a way that it interferes with future buffered operations.
For example, a TFTPDataPacket received with bufferedReceive() will
have a reference to the internal byte buffer. You must finish using
this data before calling bufferedReceive() again, or else the data
will be overwritten by the the call.
__receiveDatagram.setData(__receiveBuffer);
__receiveDatagram.setLength(__receiveBuffer.length);
_socket_.receive(__receiveDatagram);
return TFTPPacket.newTFTPPacket(__receiveDatagram);
|
public final void | bufferedSend(TFTPPacket packet)This is a special method to perform a more efficient packet send.
It should only be used after calling
{@link #beginBufferedOps beginBufferedOps() }. beginBufferedOps()
initializes a set of buffers used internally that prevent the new
allocation of a DatagramPacket and byte array for each send and receive.
To use these buffers you must call the bufferedReceive() and
bufferedSend() methods instead of send() and receive(). You must
also be certain that you don't manipulate the resulting packet in
such a way that it interferes with future buffered operations.
For example, a TFTPDataPacket received with bufferedReceive() will
have a reference to the internal byte buffer. You must finish using
this data before calling bufferedReceive() again, or else the data
will be overwritten by the the call.
_socket_.send(packet._newDatagram(__sendDatagram, _sendBuffer));
|
public final void | discardPackets()This method synchronizes a connection by discarding all packets that
may be in the local socket buffer. This method need only be called
when you implement your own TFTP client or server.
int to;
DatagramPacket datagram;
datagram = new DatagramPacket(new byte[PACKET_SIZE], PACKET_SIZE);
to = getSoTimeout();
setSoTimeout(1);
try
{
while (true)
_socket_.receive(datagram);
}
catch (SocketException e)
{
// Do nothing. We timed out so we hope we're caught up.
}
catch (InterruptedIOException e)
{
// Do nothing. We timed out so we hope we're caught up.
}
setSoTimeout(to);
|
public final void | endBufferedOps()Releases the resources used to perform buffered sends and receives.
__receiveBuffer = null;
__receiveDatagram = null;
_sendBuffer = null;
__sendDatagram = null;
|
public static final java.lang.String | getModeName(int mode)Returns the TFTP string representation of a TFTP transfer mode.
Will throw an ArrayIndexOutOfBoundsException if an invalid transfer
mode is specified.
return TFTPRequestPacket._modeStrings[mode];
|
public final TFTPPacket | receive()Receives a TFTPPacket.
DatagramPacket packet;
packet = new DatagramPacket(new byte[PACKET_SIZE], PACKET_SIZE);
_socket_.receive(packet);
return TFTPPacket.newTFTPPacket(packet);
|
public final void | send(TFTPPacket packet)Sends a TFTP packet to its destination.
_socket_.send(packet.newDatagram());
|