You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DIRECT.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
3
3
This is an extension of myjdapi to allow a direct device access without My.JDownloader.
4
4
5
-
# Theory of operation
5
+
##Theory of operation
6
6
7
7
My.JDowloader manages JDownloader devices and myjdapi provides a python interface to access them.
8
8
If possible My.JDowloader will push a direct connection to myjdapi which will be used consequently.
9
9
If enabled this JDownloader api will be available locally. The direct access modification will make
10
10
it possible to use the local api without any interaction with My.Downloader at all.
11
11
12
-
# Implemetation
12
+
##Implemetation
13
13
14
14
In myjdapi all connetions will be managed by an instance of Myjdapi. To use myjdapi locally Myjdapi needs consequently be extended to allow local connextions.
15
15
@@ -22,7 +22,7 @@ Even so the interface supports a user name and password it is not implemented ye
22
22
The call to connect_device() will ping the device to make sure it exists and it will create a device with the name given by the ip-parameter and the id 'direct'.
23
23
A direct device connection has the status connected but it has no session id since the session id is supported be My.Downloader only.
24
24
25
-
# Usage
25
+
##Usage
26
26
27
27
After myjdapi has established the connection the device can be querried as usually be calling:
0 commit comments