Netclient

In a similar way to the server (see Section 2.4.3), the end-user software can use different protocols to communicate with the server. The RouteNetClient abstract class provides a definition of what all functional network classes must provide. The class used can be specified as a parameter to the applet and so changed simply.

Functional TCP and UDP netclient classes have been developed. However, UDP cannot be used in most situations, because the applet's Security Manager prevents the reception of UDP datagrams. As UDP would only be used on embedded systems^3.4, this is not a real concern, but wasted some development time.