Define backends/modules
This commit is contained in:
parent
b607984328
commit
61b009c1ec
1 changed files with 4 additions and 4 deletions
|
|
@ -4,7 +4,7 @@ Overview
|
|||
Weboob (Web Outside Of Browsers) provides:
|
||||
|
||||
* :doc:`applications <api/tools/application/index>` to interact with websites
|
||||
* :doc:`backends <api/tools/backend>`, each one handles a specific website
|
||||
* :doc:`modules <api/tools/backend>`, each one handles a specific website
|
||||
* a :doc:`core library <api/core/index>` providing all the features needed by backends
|
||||
* :doc:`tools <api/tools/index>` to help develop backends and applications
|
||||
|
||||
|
|
@ -25,10 +25,10 @@ The core library defines capabilities. They represent features common to various
|
|||
For example, http://www.youtube.com and http://www.dailymotion.com are both videos
|
||||
providers: Weboob defines the ``CapVideo`` capability.
|
||||
|
||||
Each backend interfaces a website and implements one or many of these
|
||||
capabilities. Backends can be configured, which means that the end-user can
|
||||
Each module interfaces a website and implements one or many of these
|
||||
capabilities. Modules can be configured, which means that the end-user can
|
||||
provide personal information to access the underlaying website (login/password
|
||||
for example).
|
||||
for example). We call a configured module a Backend.
|
||||
|
||||
Multi-backend call
|
||||
------------------
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue