at:tutorial:distribution
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
at:tutorial:distribution [2007/04/26 20:16] – elisag | at:tutorial:distribution [2007/04/26 20:24] – elisag | ||
---|---|---|---|
Line 31: | Line 31: | ||
</ | </ | ||
- | When an object its exported by its actor, it becomes discoverable by other actors by means of the service type. Internally, this means that the object is placed in the export table of its actor. As shown in the example, a service type is represented by a stripe. This means that services types are not associated with a set of methods, but they denote an abstract publication topic that objects exports. As a stripe, a service type can thus be a subtype of one or more other service types. For example, an object could offer a color printing services by exporting the following stripe: | + | When an object its exported by its actor, it becomes discoverable by other actors by means of the service type. Internally, this means that the object is placed in the export table of its actor. As shown in the example, a service type is represented by a [[actors# |
< | < | ||
defstripe ColorPrinter <: Printer; | defstripe ColorPrinter <: Printer; | ||
Line 52: | Line 52: | ||
</ | </ | ||
- | The code block to execute when the service type becomes available is parameterized with the actual remote reference to the discovered service object. In the example above, '' | + | The code block to execute when the service type becomes available is parameterized with the actual remote reference to the discovered service object. In the example above, '' |
< | < | ||
We are using a future to get the return value of the '' | We are using a future to get the return value of the '' |
at/tutorial/distribution.txt · Last modified: 2009/01/30 16:13 by tvcutsem