<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- -*- coding:iso-safe-unix -*- -->
<!-- -*- coding:iso-safe-unix -*- -->
<html>
<head>
<title>Summary</title>
<meta HTTP-EQUIV="Content-Type" content="text/html;charset=US-ASCII"></head>
<body>
<li>
<tt>
<b>
<a href="tools.lisp">COM.INFORMATIMAGO.SUSV3.TOOLS</a></b></tt>
<pre>
Utilities for implementing SUSV3 API.

</pre></li>
<li>
<tt>
<b>
<a href="dirent.lisp">COM.INFORMATIMAGO.SUSV3.DIRENT</a></b></tt>
<pre>
SUSv3 dirent functions.

</pre></li>
<li>
<tt>
<b>
<a href="ipc.lisp">COM.INFORMATIMAGO.SUSV3.IPC</a></b></tt>
<pre>
An API over SUSV3-XSI IPC.

Note: The number of queues in a system is limited.
An application could use the message type as a recipient address.
cliini:  There's always another way to achieve the same thing.
But it's the lisp way to offer nice and intuitive interfaces
to achieve the stuff, otherwise we might all be using assembler.
[2005-01-02 20:30:53]
</pre></li>
<li>
<tt>
<b>
<a href="process.lisp">COM.INFORMATIMAGO.SUSV3.PROCESS</a></b></tt>
<pre>
Multiprocessing for clisp.
This package doesn't implement threads like in other Common-Lisp
implementations.  Rather it uses plain unix processes.
This has sever implications for IPC: there is no shared memory,
all inter-process communication must go thru pipes or sockets.
http://www.franz.com/support/documentation/7.0/doc/multiprocessing.htm
</pre></li></body></html>
ViewGit