Discussion

Note: At the time of writing the external ``hello world'' service is not available. However, this section has been left in for demonstration.

The connect command takes a warrant and uses it to connect to the service. It all takes place in the background, but the embedded node downloads an access point netlet, which is the launcher's link to the service. The list command lists what applications we're connected to. In this case, just the one, which has a name of our choice. Listing a particular application tells us what commands (and facets) it has.

We can see it has a command called getMessage, so we issue that command for that application. The request goes back to the main worker netlets, distributed in a redundant cluster of their own, and one of them delivers the message which the launcher returns to us.

The launcher is covered in more detail in Appendix .