官术网_书友最值得收藏!

Moodle application layers

In terms of application architecture, Moodle can be thought of as having three layers--diagrammatically looking rather like a layer cake:

By shine Oa (originally posted to Flickr as wedding cake) [CC BY 2.0 ( http://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons

At the top is the presentation layer--this displays output to the user but also accepts data from users through HTML forms. Next is the business layer and, beneath that, the data layer. The data layer is relatively easy to understand: it is where user data is maintained, where quiz questions would be stored, where grades are recorded, and so on. The business layer is where the information from the data layer is processed ready to be passed up to the presentation layer--for example, quiz questions are formed into a quiz. The business layer is also responsible for taking data from the presentation layer and processing this ready for storage by the data layer--for example, the final grade from a quiz.

In the previous section, we have been considering what the user will see (the presentation layer). At the core of Moodle sits the application data--the contents of the Moodle database. Sat between these three layers (including between the presentation layer and the user)--and the means by which application layers talk to each other--are the APIs.

主站蜘蛛池模板: 太谷县| 连南| 山东省| 淳安县| 常宁市| 儋州市| 丘北县| 卢龙县| 永安市| 深圳市| 乐山市| 昌宁县| 平安县| 房产| 桓仁| 陇南市| 平陆县| 阿鲁科尔沁旗| 灵台县| 邢台县| 巴塘县| 都江堰市| 丰台区| 和林格尔县| 海城市| 九龙城区| 麻江县| 玉林市| 辉县市| 宁武县| 綦江县| 罗源县| 沈阳市| 百色市| 新竹市| 溧水县| 中西区| 庐江县| 青海省| 兴安盟| 弋阳县|