Obsolete:MNET 1.0 RPC: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
So we want to preserve those capabilities... Additionally, we want to make sure the RPC calls are safe, and cannot be exposed by accident. | So we want to preserve those capabilities... Additionally, we want to make sure the RPC calls are safe, and cannot be exposed by accident. | ||
= Outline of a new mnet API = | |||
Calls can be exposed via the mnet API by | |||
* Moodle core | |||
* Moodle auth plugins | |||
* Moodle enrol plugins | |||
* Moodle modules | |||
== Expose an entry point == | |||
Revision as of 03:45, 4 September 2006
As part of the [Community hub] infrastructure, we need to define RPC calling conventions...
Moodle's APIs follow several principles that make them scalable annd flexible.
- They are "Just In Time discoverable" rather than all registered at runtime. This is a good optimization for HTTP's statelesness.
- Once an entry point is hit (a webpage in moodle, for instance) the module code author is in control. The framework doesn't limit what kinds of interactions can happen.
So we want to preserve those capabilities... Additionally, we want to make sure the RPC calls are safe, and cannot be exposed by accident.
Outline of a new mnet API
Calls can be exposed via the mnet API by
- Moodle core
- Moodle auth plugins
- Moodle enrol plugins
- Moodle modules
