Aquesta pàgina forma part de la documentació de Moodle en català, tot i que no ha estat traduïda encara. Podeu contribuir obertament a les tasques de traducció. Podeu consultar la Guia d'edició de la documentació i també participar ens els debats del fòrum de traductors de la documentació a moodle.org

Publishflow Block : MNET Services

De MoodleDocs
La revisió el 20:27, 28 des 2010 per Valery Fremaux (discussió | contribucions) (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....)
(dif.) ← Versió més antiga | Versió actual (dif.) | Versió més nova → (dif.)
Salta a:navegació, cerca

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 ().