at:tutorial:distribution
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:tutorial:distribution [2009/01/29 15:19] – elisag | at:tutorial:distribution [2009/01/29 15:22] – elisag | ||
---|---|---|---|
Line 253: | Line 253: | ||
On the client side, taking offline an object results in a permanent disconnection of the remote far references pointing to it. In other words, despite having network connection, unexporting an object renders remote far references permanently disconnected. This implies that client have to deal explicitly with unexported objects. | On the client side, taking offline an object results in a permanent disconnection of the remote far references pointing to it. In other words, despite having network connection, unexporting an object renders remote far references permanently disconnected. This implies that client have to deal explicitly with unexported objects. | ||
- | Clients can get notified when an object is taken offline by means of '' | + | Clients can get notified when an object is taken offline by means of '' |
Additionally, | Additionally, | ||
+ | < | ||
when: messenger takenOffline: | when: messenger takenOffline: | ||
system.println(" | system.println(" | ||
//clean certain resources associated to the buddy | //clean certain resources associated to the buddy | ||
}; | }; | ||
+ | </ | ||
- | + | The construct takes as parameter a far reference and a block of code that is executed when the taken offline event is notified to the virtual machine. '' | |
- | The construct takes as parameter a far reference and a block of code that is executed when the taken offline event is notified to the virtual machine. '' | + | |
< | < |
at/tutorial/distribution.txt · Last modified: 2009/01/30 16:13 by tvcutsem