Difference between revisions of "REST and WebService architectures"
| Line 1: | Line 1: | ||
| + | <span data-link_translate_ar_title="أبنية الراحة وخدمة ويب" data-link_translate_ar_url="%D8%A3%D8%A8%D9%86%D9%8A%D8%A9+%D8%A7%D9%84%D8%B1%D8%A7%D8%AD%D8%A9+%D9%88%D8%AE%D8%AF%D9%85%D8%A9+%D9%88%D9%8A%D8%A8"></span>[[:ar:أبنية الراحة وخدمة ويب]][[ar:أبنية الراحة وخدمة ويب]] | ||
<span data-link_translate_zh_title="休息和 web 服务的体系结构" data-link_translate_zh_url="%E4%BC%91%E6%81%AF%E5%92%8C+web+%E6%9C%8D%E5%8A%A1%E7%9A%84%E4%BD%93%E7%B3%BB%E7%BB%93%E6%9E%84"></span>[[:zh:休息和 web 服务的体系结构]][[zh:休息和 web 服务的体系结构]] | <span data-link_translate_zh_title="休息和 web 服务的体系结构" data-link_translate_zh_url="%E4%BC%91%E6%81%AF%E5%92%8C+web+%E6%9C%8D%E5%8A%A1%E7%9A%84%E4%BD%93%E7%B3%BB%E7%BB%93%E6%9E%84"></span>[[:zh:休息和 web 服务的体系结构]][[zh:休息和 web 服务的体系结构]] | ||
<span data-link_translate_ro_title="ODIHNĂ şi WebService arhitecturi" data-link_translate_ro_url="ODIHN%C4%82+%C5%9Fi+WebService+arhitecturi"></span>[[:ro:ODIHNĂ şi WebService arhitecturi]][[ro:ODIHNĂ şi WebService arhitecturi]] | <span data-link_translate_ro_title="ODIHNĂ şi WebService arhitecturi" data-link_translate_ro_url="ODIHN%C4%82+%C5%9Fi+WebService+arhitecturi"></span>[[:ro:ODIHNĂ şi WebService arhitecturi]][[ro:ODIHNĂ şi WebService arhitecturi]] | ||
Revision as of 12:20, 18 November 2015
ar:أبنية الراحة وخدمة ويب zh:休息和 web 服务的体系结构 ro:ODIHNĂ şi WebService arhitecturi pl:Architektury REST i WebService de:REST- und WebService-Architekturen nl:RUST en WebService platforms it:Architetture di resto e WebService pt:Arquiteturas de descanso e WebService es:Arquitecturas de resto y WebService fr:Architectures REST & WebService
This article has been created by an automatic translation software. You can view the article source here.
Introduction
With which architecture is the API compatible ?
Explanation
Ikoula API proposes an approach following two architectures : WebService & REST .
WebService
L'architecture WebService s'utilise :
- either get (formatting settings directly in the URI ) required for authentication settings
- in POST (passing the parameters in data table )
- either by mixing the 2 (GET and POST settings )
Here are some examples :
- Lister account VM
- https://api.ikoula.com/index.php?r=wsflex/vmlist&login=mail@example.com&crypted_password=encrypted_password&signature=xxxxxxxxxxxxxxxxxxxxxxxxxxx
- Retrieving information from a VM by using its name
- https://api.ikoula.com/index.php?r=wsflex/vminfo&login=mail@example.com&crypted_password=encrypted_password&vm_name=1234hpv56789&signature=xxxxxxxxxxxxxxxxxxxxxxxxxxx
REST
L'architecture REST s'utilise en formatant les paramètres dans l'URI et la méthode HTTP adéquate à l'action désirée.
Here are some examples :
- Returns the status of the VM "VMID "
- GET /rest/vm/:vmid
- Starts the VM "VMID "
- POST /rest/vm/:vmid/status /Start
- Removes the snapshot "snapshot Name " the VM "VMID "
- DELETE /rest/vm/:vmid/snapshot /:snapshot Name
Passing the authentication settings (see WIKI on the Authentication and security For more details ), here is an example URL :
https://api.ikoula.com/rest/vm/list?login=mail@example.com&crypted_password=encrypted_password&signature=xxxxxxxxxxxxxxxxxxxxxxxxxxx
This article seemed you to be useful ?
<comments />
Enable comment auto-refresher