Access points' communication

The main thing missing is that the access point netlet, the one we just wrote to give the client access to the service, is entirely self-contained and isn't part of a distributed application. This isn't the way things need to be; it's just we chose to write a very simple example.

In practice a netlet can happily make network connections (see Chapter  and the document Programming with Jtrix: The Beatrix application framework. In fact, an access point netlet will want to keep up to date with several other netlets as we described in the Hello world service 3 earlier. This federated approach is what Beatrix is really good at.

It shouldn't be surprising that helping a netlet communicate with its peers is not part of the Jtrix core and is instead part of Beatrix, an optional extra. This is because Jtrix doesn't impose any networking standards of its own. Your application is free to use whatever is best for it: SOAP, RMI, HTTP or anything else.