blocks:remotecontent
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| blocks:remotecontent [2017/04/13 16:02] – [Description] admin | blocks:remotecontent [2025/12/10 16:16] (Version actuelle) – modification externe 127.0.0.1 | ||
|---|---|---|---|
| Ligne 51: | Ligne 51: | ||
| The capture mode based on start and end patterns assume there are such recognizable patterns in the received content flow. This is not always tivial. We will examine how to use a Dom parser to extract a portion of content based on a XPath identifier that would be more flexible to cut an interesting content sequence. | The capture mode based on start and end patterns assume there are such recognizable patterns in the received content flow. This is not always tivial. We will examine how to use a Dom parser to extract a portion of content based on a XPath identifier that would be more flexible to cut an interesting content sequence. | ||
| - | ==== dynamic | + | ==== Dynamic |
| In some cases, (still in study) we will allow internal dynamic values injection in the remote queries (such as username, user id o idnumber, course idnumber or shortname, etc... in general any available contextual available data that might be usefull to divert the remote server reponse) | In some cases, (still in study) we will allow internal dynamic values injection in the remote queries (such as username, user id o idnumber, course idnumber or shortname, etc... in general any available contextual available data that might be usefull to divert the remote server reponse) | ||
blocks/remotecontent.1492099372.txt.gz · Dernière modification : (modification externe)