2011-11-09 11:33:19 +04:00
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
2015-08-25 09:01:42 +03:00
|
|
|
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
|
2011-11-09 11:33:19 +04:00
|
|
|
<pkgmetadata>
|
2016-01-25 16:13:40 +03:00
|
|
|
<maintainer type="project">
|
|
|
|
|
<email>crypto@gentoo.org</email>
|
|
|
|
|
<name>Crypto</name>
|
|
|
|
|
</maintainer>
|
2011-11-09 11:33:19 +04:00
|
|
|
<longdescription>
|
|
|
|
|
In an ideal world, Assuan is irrelevant. Assuan's primary use is to
|
|
|
|
|
allow a client to interact with a non-persistent server. Using Assuan,
|
|
|
|
|
this is accomplished by forking a subprocess and communicating with it
|
|
|
|
|
via, for example, a pipe or unix domain socket. This method is neither
|
|
|
|
|
elegant nor efficient especially when there is a lot of data spread
|
|
|
|
|
across several transactions: not only is there a penalty for an
|
|
|
|
|
increased number of context switches, but also a significant amount of
|
|
|
|
|
data is MEMCPYed from the client to a file descriptor and from the file
|
|
|
|
|
descriptor to the server.
|
|
|
|
|
</longdescription>
|
|
|
|
|
</pkgmetadata>
|
