You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by bl...@apache.org on 2002/09/26 20:34:12 UTC
cvs commit: jakarta-avalon-excalibur/event/src/xdocs thread-howto.xml menu.xml
bloritsch 2002/09/26 11:34:12
Modified: event/src/xdocs menu.xml
Added: event/src/xdocs thread-howto.xml
Log:
add howto for cpuparser
Revision Changes Path
1.8 +0 -2 jakarta-avalon-excalibur/event/src/xdocs/menu.xml
Index: menu.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-excalibur/event/src/xdocs/menu.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- menu.xml 26 Sep 2002 18:22:06 -0000 1.7
+++ menu.xml 26 Sep 2002 18:34:12 -0000 1.8
@@ -26,9 +26,7 @@
<item href="thread-howto.html" name="Use Thread Pools"/>
-->
<item href="util-howto.html" name="Use System Util"/>
-<!--
<item href="cpuparser-howto.html" name="Extend System Util"/>
--->
</menu>
</body>
</project>
1.1 jakarta-avalon-excalibur/event/src/xdocs/thread-howto.xml
Index: thread-howto.xml
===================================================================
<?xml version="1.0"?>
<document>
<header>
<title>Excalibur Event - Overview</title>
<authors>
<person name="Berin Loritsch" email="bloritsch@apache.org"/>
</authors>
</header>
<body>
<s1 title="Introduction">
<p>
This is the Excalibur Event package which includes event queues,
asynchronous command processing, and the interfaces to support
event based programming. Event is heavily influenced by Matt
Welsh's work with the
<fork href="http://www.cs.berkeley.edu/~mdw/proj/seda/">SEDA architecture</fork>.
We forked the portion of his SandStorm server that had to do with
event processing. From there we cleaned up the API and made it as
generic as we could.
</p>
<p>
The Event package actually has five related sub packages inside
of it. Event is the basic interfaces for the Queues, Sinks,
Sources, etc. Command houses code for the CommandManager so that
your code can safely process Commands (a type of event) in the
background. MPool, short for Managed Pool, houses code for a
pool implementation that manages its size asynchronously so you
don't have to worry about it. Thread is the thread pool code
which uses MPool to keep track of the threads. Lastly, Util
provides some basic utilities so that we can programatically
determine the number of processors your hardware has.
</p>
</s1>
</body>
<footer>
<legal>
Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
$Revision: 1.1 $ $Date: 2002/09/26 18:34:12 $
</legal>
</footer>
</document>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>