[Home]DotNetSockets

BOOST WIKI | RecentChanges | Preferences | Page List | Links List

Difference (from prior major revision) (minor diff)

Changed: 3c3
Here is an UML diagram with the most important stuff of the net library in the .NET Framework 1.1.
Here is a UML diagram with the most important stuff of the net library in .NET Framework 1.1.

Changed: 10c10
* The socket class supports a synchronous and an asynchronous I/O model. There is just one interface for an asynchronous I/O model - the implementation is hidden in the library. It is unknown to the library user if the implementation is based on multiplexing, aio, I/O completionports etc.
* Socket supports a synchronous and an asynchronous I/O model. There is just one interface for an asynchronous I/O model - the implementation is hidden in the library. It is unknown to the library user if the implementation is based on multiplexing, aio, I/O completionports etc.

.NET Framework 1.1

Here is a UML diagram with the most important stuff of the net library in .NET Framework 1.1.

In .NET you either work with Socket directly or use one of the helper classes TcpClient, TcpListener and UdpClient. They are all based on Socket as you can see. For reading and writing you either call methods of Socket or use the NetworkStream class of TcpClient. This class isn't in the UML diagram as it has similar methods as Socket for reading and writing. It supports the synchronous and asynchronous I/O model as well.

Good:

Bad:


BOOST WIKI | RecentChanges | Preferences | Page List | Links List
Edit text of this page | View other revisions
Last edited March 5, 2005 4:21 pm (diff)
Search:
Disclaimer: This site not officially maintained by Boost Developers