aboutsummaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorMarcus Brinkmann <[email protected]>2008-03-11 16:05:40 +0000
committerMarcus Brinkmann <[email protected]>2008-03-11 16:05:40 +0000
commit3dcae464f4944258b2f36f4e85b509940733a682 (patch)
tree1cb1168f01cb1d506d0947ffe54f97a578633bac /TODO
parent2008-03-06 Marcus Brinkmann <[email protected]> (diff)
downloadgpgme-3dcae464f4944258b2f36f4e85b509940733a682.tar.gz
gpgme-3dcae464f4944258b2f36f4e85b509940733a682.zip
doc/
2008-03-11 Marcus Brinkmann <[email protected]> * gpgme.texi (File Based Data Buffers): Document the need for blocking operations. (Callback Based Data Buffers): Likewise. gpgme/ 2008-03-11 Marcus Brinkmann <[email protected]> * data.c (gpgme_data_read, gpgme_data_write): Retry on EINTR.
Diffstat (limited to 'TODO')
-rw-r--r--TODO9
1 files changed, 9 insertions, 0 deletions
diff --git a/TODO b/TODO
index 56b58ac5..2c180e03 100644
--- a/TODO
+++ b/TODO
@@ -41,6 +41,15 @@ Hey Emacs, this is -*- outline -*- mode!
There is a configure time warning, though.
* New features:
+** Flow control for data objects.
+ Currently, gpgme_data_t objects are assumed to be blocking. To
+ break this assumption, we need either (A) a way for an user I/O
+ callback to store the current operation in a continuation that can
+ be resumed later. While the continuation exists, file descriptors
+ associated with this operation must be removed from their
+ respective event loop. or (B) a way for gpgme data objects to be
+ associated with a waitable object, that can be registered with the
+ user event loop. Neither is particularly simple.
** Extended notation support. When gpg supports arbitrary binary
notation data, provide a user interface for that.
** notification system