Abstract base class for TCP_LWIP send queues. More...

#include <TcpLwipQueues.h>

Inheritance diagram for inet::tcp::TcpLwipSendQueue:

Public Member Functions
	TcpLwipSendQueue ()
	Ctor. More...

virtual	~TcpLwipSendQueue ()
	Virtual dtor. More...

virtual void	setConnection (TcpLwipConnection *connP)
	set connection queue, and initialise queue variables. More...

virtual void	enqueueAppData (cPacket *msgP)=0
	Called on SEND app command, it inserts in the queue the data the user wants to send. More...

virtual unsigned int	getBytesForTcpLayer (void *bufferP, unsigned int bufferLengthP) const =0
	Copy data to the buffer for send to LWIP. More...

virtual void	dequeueTcpLayerMsg (unsigned int msgLengthP)=0
	This function should remove msgLengthP bytes from TCP layer queue. More...

virtual unsigned long	getBytesAvailable () const =0
	Utility function: returns how many bytes are available in the queue. More...

virtual TCPSegment *	createSegmentWithBytes (const void *tcpDataP, unsigned int tcpLengthP)=0
	Called when the TCP wants to send or retransmit data, it constructs a TCP segment which contains the data from the requested sequence number range. More...

Protected Attributes
TcpLwipConnection *	connM

Detailed Description

Abstract base class for TCP_LWIP send queues.

In fact a single object represents both the send queue and the retransmission queue (no need to separate them). The TCPConnection object knows which data in the queue have already been transmitted ("retransmission queue") and which not ("send queue"). This class is not interested in where's the boundary.

There is another particularity about this class: as a retransmission queue, it stores bytes and not segments. TCP is a bytestream oriented protocol (sequence numbers refer to bytes and not to TPDUs as e.g. in ISO TP4), and the protocol doesn't rely on retransmitted segments having the same segment boundaries as the original segments. Some implementations store segments on the retransmission queue, and others store only the data bytes; RFCs explicitly allow both. (See e.g. RFC1122 p90, section 4.2.2.15, "IMPLEMENTATION" note).

To simulate a TCP that retains segment boundaries in retransmissions, the appropriate TCPAlgorithm class should remember where the segment boundaries were at the original transmission, and it should form identical segments when retransmitting. The createSegmentWithBytes() send queue method makes this possible.

This class is polymorphic because depending on where and how you use the TCP model you might have different ideas about "sending data" on a simulated connection.

You might want to:

transmit a real bytes, especially if the application which uses TCP is a ported version of a real socket application.
simulate a "dummy" connection, that is, simulated TCP segments contain do not contain any real data, only the number of bytes they represent. You'll want to do this when the app is there solely as a traffic generator (e.g. simulated file transfer or telnet session), but actual data is unimportant.
transmit a sequence of cMessage objects, and you want exactly the same cMessage sequence to be reproduced on the receiver side. Here every cMessage maps to a sequence number range in the TCP stream, and the object is passed up to the application on the receiving side when its last byte has arrived on the simulated connection.

Different TcpLwipSendQueue subclasses can be written to accomodate different needs.

This class goes hand-in-hand with TcpLwipReceiveQueue.

See also: TcpLwipReceiveQueue

Constructor & Destructor Documentation

inet::tcp::TcpLwipSendQueue::TcpLwipSendQueue ( )

inline

Ctor.

91 : connM(nullptr) {}

inet::tcp::TcpLwipSendQueue::connM

TcpLwipConnection * connM

Definition: TcpLwipQueues.h:145

virtual inet::tcp::TcpLwipSendQueue::~TcpLwipSendQueue ( )

inlinevirtual

Virtual dtor.

96 {}

Member Function Documentation

virtual TCPSegment* inet::tcp::TcpLwipSendQueue::createSegmentWithBytes	(	const void *	tcpDataP,
		unsigned int	tcpLengthP
	)

pure virtual

Called when the TCP wants to send or retransmit data, it constructs a TCP segment which contains the data from the requested sequence number range.

The actually returned segment may contain less then maxNumBytes bytes if the subclass wants to reproduce the original segment boundaries when retransmitting.

called from inside of send_callback() called before called the send() to IP layer

Implemented in inet::tcp::TcpLwipMsgBasedSendQueue, inet::tcp::TcpLwipByteStreamSendQueue, and inet::tcp::TcpLwipVirtualDataSendQueue.

Referenced by inet::tcp::TCP_lwIP::ip_output().

virtual void inet::tcp::TcpLwipSendQueue::dequeueTcpLayerMsg ( unsigned int msgLengthP )

pure virtual

This function should remove msgLengthP bytes from TCP layer queue.

Implemented in inet::tcp::TcpLwipMsgBasedSendQueue, inet::tcp::TcpLwipByteStreamSendQueue, and inet::tcp::TcpLwipVirtualDataSendQueue.

Referenced by inet::tcp::TcpLwipConnection::do_SEND().

virtual void inet::tcp::TcpLwipSendQueue::enqueueAppData ( cPacket * msgP )

pure virtual

Called on SEND app command, it inserts in the queue the data the user wants to send.

Implementations of this abstract class will decide what this means: copying actual bytes, just increasing the "last byte queued" variable, or storing cMessage object(s). The msg object should not be referenced after this point (sendQueue may delete it.)

Implemented in inet::tcp::TcpLwipMsgBasedSendQueue, inet::tcp::TcpLwipByteStreamSendQueue, and inet::tcp::TcpLwipVirtualDataSendQueue.

Referenced by inet::tcp::TcpLwipConnection::send().

virtual unsigned long inet::tcp::TcpLwipSendQueue::getBytesAvailable ( ) const

pure virtual

Utility function: returns how many bytes are available in the queue.

Implemented in inet::tcp::TcpLwipMsgBasedSendQueue, inet::tcp::TcpLwipByteStreamSendQueue, and inet::tcp::TcpLwipVirtualDataSendQueue.

Referenced by inet::tcp::TcpLwipConnection::close(), and inet::tcp::TcpLwipConnection::do_SEND().