#c #kernel
The principle of separation of mechanism and policy is the substantial difference between the philosophy of micro and monolithic kernels.[25][26] Here a mechanism is the support that allows the implementation of many different policies, while a policy is a particular "mode of operation". Example:
- Mechanism: User login attempts are routed to an authorization server
- Policy: Authorization server requires a password which is verified against stored passwords in a database
If you want to change selection, open document below and click on "Move attachment"
Kernel-process communication (IPC). Kernel-wide design approaches Naturally, the above listed tasks and features can be provided in many ways that differ from each other in design and implementation. <span>The principle of separation of mechanism and policy is the substantial difference between the philosophy of micro and monolithic kernels.[25][26] Here a mechanism is the support that allows the implementation of many different policies, while a policy is a particular "mode of operation". Example: Mechanism: User login attempts are routed to an authorization server Policy: Authorization server requires a password which is verified against stored passwords in a database Because the mechanism and policy are separated, the policy can be easily changed to e.g. require the use of a security token. In minimal microkernel just some very basic policies are in Summary
| status | not read | | reprioritisations | |
|---|
| last reprioritisation on | | | suggested re-reading day | |
|---|
| started reading on | | | finished reading on | |
|---|
Details