Publishflow Block : MNET Services: Difference between revisions
(New page: Publishflow implements a set of MNET services in order to perform proper across MNET operations. Here comes the list of MNET XML-RPC functions that are provided by the blocks XML-RPC API....) |
|||
| Line 23: | Line 23: | ||
delivery_deliver() : get a course backup from a remote platform. If data transfer is done using local file system, will only give information about the physical location of a course archive. | delivery_deliver() : get a course backup from a remote platform. If data transfer is done using local file system, will only give information about the physical location of a course archive. | ||
delivery_deploy() : deploys a course archive where called. This function has to be called remotely from the archive originator that will drive the deployement process (). | delivery_deploy() : deploys a course archive where called. This function has to be called remotely from the archive originator that will drive the deployement process (i.e. the deployment IS NOT initiated from the platform you want the course coming in, but where it goes out). | ||
delivery_publish() : similar to the deployment function, but there are some particularities when dealing between a Course Factory and a Course Catalog Moodle instances. | |||
publishflow_updateplatforms() : This function is called by other hosts in a MNET to explore the network and determine which instances are in the MNET neighborhood. | |||
Revision as of 20:32, 28 December 2010
Publishflow implements a set of MNET services in order to perform proper across MNET operations.
Here comes the list of MNET XML-RPC functions that are provided by the blocks XML-RPC API.
Please note that the XML-RPC API applied to blocks need using a published patch adding XML-RPC support to blocks in Moodle 1.9. This support is now fully available in Moodle 2.0, although this block is not yet ported forth.
Service : coursedelivery_data
Description
This service is used to transport information about courses between platforms. NOT FINALIZED.
Functions
delivery_get_sessions() : get information about remotely deployed instances of a course template. Till now, we have feared to interfer too much wich core database model and use the IDNumber of the course to identify similarity between distinct course volumes. i.e. all courses sharing the same value of IDNumber are considered as being instances of an originating course in a factory node.
Service : coursedelivery_admin
This service is used to register course delivery commands.
Functions
delivery_deliver() : get a course backup from a remote platform. If data transfer is done using local file system, will only give information about the physical location of a course archive.
delivery_deploy() : deploys a course archive where called. This function has to be called remotely from the archive originator that will drive the deployement process (i.e. the deployment IS NOT initiated from the platform you want the course coming in, but where it goes out).
delivery_publish() : similar to the deployment function, but there are some particularities when dealing between a Course Factory and a Course Catalog Moodle instances.
publishflow_updateplatforms() : This function is called by other hosts in a MNET to explore the network and determine which instances are in the MNET neighborhood.
