avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From blorit...@apache.org
Subject cvs commit: jakarta-avalon-excalibur/event/src/xdocs thread-howto.xml
Date Thu, 26 Sep 2002 18:36:38 GMT
bloritsch    2002/09/26 11:36:38

  Modified:    event/src/xdocs thread-howto.xml
  real docs for Thread-Howto--will be pulled RSN
  Revision  Changes    Path
  1.2       +6 -23     jakarta-avalon-excalibur/event/src/xdocs/thread-howto.xml
  Index: thread-howto.xml
  RCS file: /home/cvs/jakarta-avalon-excalibur/event/src/xdocs/thread-howto.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- thread-howto.xml	26 Sep 2002 18:34:12 -0000	1.1
  +++ thread-howto.xml	26 Sep 2002 18:36:38 -0000	1.2
  @@ -2,34 +2,17 @@
  -    <title>Excalibur Event - Overview</title>
  +    <title>Excalibur Event - How To Use Thread</title>
         <person name="Berin Loritsch" email="bloritsch@apache.org"/>
  -    <s1 title="Introduction">
  +    <s1 title="Don't">
  -        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.
  +        This will be going away really soon, so I do not want
  +        you to get used to using it.  We have a plan in place
  +        to make MPool and Thread work happily together.

To unsubscribe, e-mail:   <mailto:avalon-cvs-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-cvs-help@jakarta.apache.org>

View raw message