Browse Prior Art Database

Change in Receive Flow for NetBios Protocol

IP.com Disclosure Number: IPCOM000106807D
Original Publication Date: 1993-Dec-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 2 page(s) / 70K

Publishing Venue

IBM

Related People

Anand, VK: AUTHOR

Abstract

Most NetBIOS applications know the size of the data they will receive, so the applications issue receives with approximately the size of the buffers. However, there are other NetBIOS applications which do not know the size of the data the applications will receive. This invention would help the second category of the applications. An example of the second category would be Transport Layer Protocol Boundary (TLPB) which provides an interface for a socket-based application to communicate with any Socket or NetBIOS applications using the NetBIOS Protocol Stack. A socket is an abstraction provided by Berkeley 4BSD UNIX which usually allows an application program to access the TCP/IP protocols. An application opens a socket, specifies the service desired, e.g.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Change in Receive Flow for NetBios Protocol

      Most NetBIOS applications know the size of the data they will
receive, so the applications issue receives with approximately the
size of the buffers.  However, there are other NetBIOS applications
which do not know the size of the data the applications will receive.
This invention would help the second category of the applications.
An example of the second category would be Transport Layer Protocol
Boundary (TLPB) which provides an interface for a socket-based
application to communicate with any Socket or NetBIOS applications
using the NetBIOS Protocol Stack.  A socket is an abstraction
provided by Berkeley 4BSD UNIX which usually allows an application
program to access the TCP/IP protocols.  An application opens a
socket, specifies the service desired, e.g., reliable stream
delivery, binds the socket to a specific distinction and then sends
or receives data.  These Socket applications would not know the
receive data size, since they use NetBIOS Protocol as a non-native
network.

      This leads to a problem when Socket applications do not have
enough buffers for their receive commands, NetBIOS copies as much
data from the data frame to the receive buffer as it can and searches
to find another receive for that session.  If it can find another
receive pending that it can use to receive the data, then it will
send a receive outstanding frame acknowledging the bytes accepted and
informing its partner that it has more receive commands available but
the partner has to reframe the data and send it back.  This leads to
many of receive-outstanding frames sent on the wire and the partner
has to reframe the data which consumes time.  In addition, if the
partner has issued a send with a timeout period, the send will not
complete and the session will come down.  The...