The Server Framework provides TCP and UDP
client and
server classes which handle all of the details of the connections that you are making and receiving. You hook into these classes by implementing methods on
callback interfaces that are supplied to the server or client object in their constructor. Although the callback interfaces are quite large, there are several helper classes which implement
null objects for the callback interfaces so that you can simply implement only the methods that interest you. As you'll see from the later tutorials, for a
TCP server this could be as simple as implementing two callback methods and for a
UDP server just one!
Callback interfaces are built up using quite a deep inheritance heirarchy, but for each of the main types of
socket the most derived interface is probably the one that you'll implement:
And these are the default implementations:
Note that there's only a default implementation for
IStreamSocketServerExCallback as this can be used where instances of
IStreamSocketServerCallback and
IStreamSocketConnectionManagerCallback are required.
See the
client and
server tutorials and the
interface documentation for details of how and when to implement the various methods on the callback interfaces.
See the
lifecycle of a stream socket connection for details about when each of the callbacks gets called and what you can or can not expect to be able to do when they're called.
