Meta-Transport Library, A protocol base class library. Release 1.1 [report]

T. Strayer
1994 unpublished
DISCLAIMER This report was prepared as an account of work sponsoredby an agency of the United States Government. Neither the United States Government nor any agency thereof, nor any of their employees, makes any warranty, express o_ implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any
more » ... erein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. f There are two central data structures, the packet and the context. The protocol procedures operate on these structures. Packets require construction, data insertion, transmission, reception, and data retrieval. The endpoint state structure is changed according to the parsing of packets and the servicing of user requests. In both cases there is a central repository of data and actors, or methods, on the reposed data. This profile matches the definition of an object.
doi:10.2172/10150462 fatcat:ktuspykntrgsblcik73dc6vam4