Comments on: A proposal of interoperability architecture for Moodle http://blogs.dfwikilabs.org/moodle_ws/2008/04/14/a-proposal-of-interoperability-architecture-for-moodle/ Development Blog about the Moodle Webservices API and interoperability Issues Fri, 29 Aug 2008 18:21:17 +0000 http://wordpress.org/?v=2.3.1 By: Moodle WebServices » I want it all: kinds of webservices in moodle. http://blogs.dfwikilabs.org/moodle_ws/2008/04/14/a-proposal-of-interoperability-architecture-for-moodle/#comment-50 Moodle WebServices » I want it all: kinds of webservices in moodle. Thu, 10 Jul 2008 08:42:39 +0000 http://blogs.dfwikilabs.org/moodle_ws/2008/04/14/a-proposal-of-interoperability-architecture-for-moodle/#comment-50 [...] doing great things, and in the campus project we did some good job too. But the  goo thing of the proposed architecture that David and Ferran came up with is that allows the posibility of writting connectors [...] […] doing great things, and in the campus project we did some good job too. But the  goo thing of the proposed architecture that David and Ferran came up with is that allows the posibility of writting connectors […]

]]> By: ludo http://blogs.dfwikilabs.org/moodle_ws/2008/04/14/a-proposal-of-interoperability-architecture-for-moodle/#comment-9 ludo Thu, 12 Jun 2008 06:15:50 +0000 http://blogs.dfwikilabs.org/moodle_ws/2008/04/14/a-proposal-of-interoperability-architecture-for-moodle/#comment-9 It means that we call the Moodle core APIs we DO NOT access directly to the database and other persistence objects. Everithing needs to be done (and is being done) using the Moodle core functions. This functions howevera are scattered all over Moodle and this layers provides with ONE handle to rule them all ;-) The idea is that when the API is implemented tested and stable, the Moodle core team with refactor some of the functions to boos efficiency and evens some parts of moodle migth use this very layer to access the information. THis layers migth be the first step towarts a more structured core of moodle both for external developers and for moodle module developers. Cheers Ludo It means that we call the Moodle core APIs we DO NOT access directly to the database and other persistence objects. Everithing needs to be done (and is being done) using the Moodle core functions. This functions howevera are scattered all over Moodle and this layers provides with ONE handle to rule them all ;-)
The idea is that when the API is implemented tested and stable, the Moodle core team with refactor some of the functions to boos efficiency and evens some parts of moodle migth use this very layer to access the information.
THis layers migth be the first step towarts a more structured core of moodle both for external developers and for moodle module developers.
Cheers
Ludo

]]> By: Rahim http://blogs.dfwikilabs.org/moodle_ws/2008/04/14/a-proposal-of-interoperability-architecture-for-moodle/#comment-8 Rahim Wed, 11 Jun 2008 17:39:20 +0000 http://blogs.dfwikilabs.org/moodle_ws/2008/04/14/a-proposal-of-interoperability-architecture-for-moodle/#comment-8 I was curious about the following: "Integration layer: This layer consists on THE API (being implemented) that provides a one point access to the Moodle + contrib functionalities." Does this mean that you are calling your own functions to modify the data in the Moodle database, such as adding new users, enrolling users etc..? or are you using the functions that Moodle itself implements via the core? I was curious about the following:

“Integration layer: This layer consists on THE API (being implemented) that provides a one point access to the Moodle + contrib functionalities.”

Does this mean that you are calling your own functions to modify the data in the Moodle database, such as adding new users, enrolling users etc..? or are you using the functions that Moodle itself implements via the core?

]]>