summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoe Rayhawk <jrayhawk@freedesktop.org>2013-05-18 02:28:53 -0700
committerJoe Rayhawk <jrayhawk@freedesktop.org>2013-05-18 02:28:53 -0700
commit1c1de8ee1540372560a488696cc510772ad594c3 (patch)
treed35fbf3fc36e84013728f5a30d0cc03330074337
parentb1a220bc8d4e210b719bd628cdd2c108fd8e04b7 (diff)
moin2mdwn: convert page ScanService
-rw-r--r--ScanService.mdwn48
-rw-r--r--ScanService.moin47
2 files changed, 48 insertions, 47 deletions
diff --git a/ScanService.mdwn b/ScanService.mdwn
new file mode 100644
index 00000000..6a49f75e
--- /dev/null
+++ b/ScanService.mdwn
@@ -0,0 +1,48 @@
+
+{i} This page state about a scanner service in freedesktop. This document was started off a discussion at xdg mailing list : [[http://lists.freedesktop.org/archives/xdg/2007-January/009074.html|http://lists.freedesktop.org/archives/xdg/2007-January/009074.html]]
+
+
+## Goals
+
+* Monitor buttons
+* Share devices
+These feature imply that the software own the device handle, this is why the software expose acquisition API.
+
+* Acquire image
+
+## Achievement
+
+This can be done through a dbus system wide daemon.
+
+
+## DBus API
+
+This is a rough draft of an API -- [[EtienneBersac|EtienneBersac]] 2007-01-28 22:21:45
+
+* device_list [[GetDeviceList|GetDeviceList]]
+* string [[GetDeviceInfo|GetDeviceInfo]] (device)
+* option_list [[GetDeviceOptions|GetDeviceOptions]] (device)
+* [[ShareDevice|ShareDevice]] (device, boolean)
+* job [[StartScan|StartScan]] (device, settings)
+* [[StopScan|StopScan]] (job)
+* [[GetImage|GetImage]] (job)
+/!\ How to monitor ? How to get buttons events ? How should the image be transferred back to the client?
+
+* A file descriptor or device node might be one way for transferring the image quickly (sending it directly over D-BUS definitely wouldn't work).
+Signals :
+
+* device-plugged (device)
+* device-unplugged
+* button-pressed (device, button)
+* job-done (job)
+
+## Scanner access
+
+Scanner access is done through the famous SANE library. Hope that HAL & SANE will work better together in the future in order to get devices from HAL.
+
+
+## Sharing
+
+SANE has a net scanning protocol. However, it shows some limitation (basically, it's too slow for huge image). What to do ?
+
+* It would be nice to come up with a new protocol for this like the D-BUS one, maybe with some kind of compression, like bzip2. I wouldn't worry about breaking compatibility. -- [[DonaldStraney|DonaldStraney]] \ No newline at end of file
diff --git a/ScanService.moin b/ScanService.moin
deleted file mode 100644
index 229104bd..00000000
--- a/ScanService.moin
+++ /dev/null
@@ -1,47 +0,0 @@
-{i} This page state about a scanner service in freedesktop. This document was started off a discussion at xdg mailing list : http://lists.freedesktop.org/archives/xdg/2007-January/009074.html
-
-== Goals ==
-
- * Monitor buttons
- * Share devices
-
-These feature imply that the software own the device handle, this is why the software expose acquisition API.
-
- * Acquire image
-
-== Achievement ==
-
-This can be done through a dbus system wide daemon.
-
-== DBus API ==
-
-This is a rough draft of an API -- EtienneBersac <<DateTime(2007-01-28T22:21:45Z)>>
-
- * device_list GetDeviceList
- * string GetDeviceInfo (device)
- * option_list GetDeviceOptions (device)
- * ShareDevice (device, boolean)
- * job StartScan (device, settings)
- * StopScan (job)
- * GetImage (job)
-
-/!\ How to monitor ? How to get buttons events ? How should the image be transferred back to the client?
- A file descriptor or device node might be one way for transferring the image quickly (sending it directly over D-BUS definitely wouldn't work).
-
-Signals :
-
- * device-plugged (device)
- * device-unplugged
- * button-pressed (device, button)
- * job-done (job)
-
-== Scanner access ==
-
-Scanner access is done through the famous SANE library. Hope that HAL & SANE will work better together in the future in order to get devices from HAL.
-
-== Sharing ==
-
-SANE has a net scanning protocol. However, it shows some limitation (basically, it's too slow for huge image). What to do ?
-
- It would be nice to come up with a new protocol for this like the D-BUS one, maybe with some kind of
- compression, like bzip2. I wouldn't worry about breaking compatibility. -- DonaldStraney