unsigned short mdi_initAssociation(unsigned int remoteSideReceiverWindow, unsigned short noOfInStreams, unsigned short noOfOutStreams, unsigned int remoteInitialTSN, unsigned int tagRemote, unsigned int localInitialTSN)

This is the second function needed to fully create and initialize an association (after mdi_newAssociation()) THe association is created in two steps because data become available at the a-side in two steps
  1. associate
  2. init acknowledgement
At the z-side, with the cookie message all data is available at once.

Documentation

This is the second function needed to fully create and initialize an association (after mdi_newAssociation()) THe association is created in two steps because data become available at the a-side in two steps
  1. associate
  2. init acknowledgement
At the z-side, with the cookie message all data is available at once. So mdi_newAssociation and mdi_initAssociation must be called when the initAck with valid Cookie is received.

Parameters:
remoteSideReceiverWindow - rwnd size that the peer allowed in this association
noOfInStreams - number of incoming (receive) streams after negotiation
noOfOutStreams - number of outgoing (send) streams after negotiation
remoteInitialTSN - initial TSN of the peer
tagRemote - tag of the peer
localInitialTSN - my initial TSN, needed for initializing my flow control
Returns:
0 for success, else 1 for error

Alphabetic index HTML hierarchy of classes or Java



This page was generated with the help of DOC++.