Remote Client Communication
Remote clients are implemented as follows:
You set up an as-agent, which plays the role of a seeder and a proxy server for remote clients. Using the as-agent, you issue a remote_listen command to contact the remote client and accept incoming remote client connections. Using the C API or the Java API, you perform remote discovery to discover the remote client, and you specify a list of well known IP addresses and ports of proxy as-agents to remotely connect to.
Remote Clients and Seeding Distribution Scope
A remote client application can never become a seeder on a space. If an application that is remotely connected requests to join a space as a seeder, it will remain a leech. However, remote client applications can still create browsers or listeners with a distribution scope of "seeded." In this case, the behavior on the remote client is similar to that of a leech where tuples are not returned."