optimizing gpg for the gpgme library

[Folkert van Heusden]

Hi,

I propose the following:
split-up gpg into a front-end and a shared library. The shared library
then contains all code for handling the keyring-files, doing the
crypto-stuff, etc. while the front-end (just a normal executable)
contains the code for parsing commandlines and calling the shared
library with all the previously mentioned functions. That way, the
gpgme-library can also link against this library so that it only has to
do function-calls instead of invoking the whole gpg-executable when it
wants to do anything pgp-ish.


Folkert van Heusden

-- 
Auto te koop, zie: http://www.vanheusden.com/daihatsu.php
--------------------------------------------------------------------
Get your PGP/GPG key signed at www.biglumber.com!
--------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 282 bytes
Desc: Digital signature
Url : /pipermail/attachments/20050730/72462d40/attachment.pgp