Managed netlets have access to a resource discovery API through which they may use symbolic names to access either cluster resources or regular Jtrix Services. The mapping from symbolic name to resource or service is defined through the control API when the netlet is run. This API may be extended in the future to allow dynamic discovery of resources.
It is up to the application logic to obey the constraints imposed by the use of such resources. If an application netlet uses a persistent resource, then it is necessary for that resource to be available on any node on which the netlet is to be run. Services should in turn be prepared for a resource to be unavailable.
Such resources remain the property of the hosting contract. The controller may release such resources at any time, terminating access to the resource by managed netlets.