20 |
|
|
21 |
A server provides services to its clients. In a capability system the |
A server provides services to its clients. In a capability system the |
22 |
right to access a given service is called a capability. This right is |
right to access a given service is called a capability. This right is |
23 |
hold by a client. It was previously granted to the client by the |
held by a client. It was previously granted to the client by the |
24 |
server. The client can then make use of this right, cease it, or |
server. The client can then make use of this right, cease it, or |
25 |
transfer (copy) it to a new client. |
transfer (copy) it to a new client. |
26 |
|
|
123 |
------------------ |
------------------ |
124 |
|
|
125 |
Capability classes require a capability object definition (via storage |
Capability classes require a capability object definition (via storage |
126 |
size and constructor/desctructor callbacks), and a demuxer for |
size and constructor/destructor callbacks), and a demuxer for |
127 |
incoming RPC messages on capability objects from this class. |
incoming RPC messages on capability objects from this class. |
128 |
|
|
129 |
After creating a class, you will usually want to start a manager |
After creating a class, you will usually want to start a manager |