| Package | Description |
|---|---|
| org.agilewiki.jactor |
Introduction to JActor
|
| org.agilewiki.jactor.apc |
The apc package implements Asynchronous Procedure Calls (APC), or two-way messaging.
|
| org.agilewiki.jactor.bufferedEvents |
The bufferedEvents package supports the dispatching of one-way messages (events),
but it buffers outgoing events and sends them only when there are no other incoming events
to process, which results in a significant improvement in throughput when under load.
|
| org.agilewiki.jactor.concurrent |
The concurrent package contains a number of classes that are helpful
in delivering high-performance.
|
| org.agilewiki.jactor.continuation | |
| org.agilewiki.jactor.events |
The events package supports the dispatching of one-way messages (events).
|
| org.agilewiki.jactor.factory | |
| org.agilewiki.jactor.lpc |
Introducing JLPCActor--the Basic Actor
|
| org.agilewiki.jactor.nbLock |
NBLock provides exclusive access to a resource without blocking a thread.
|
| org.agilewiki.jactor.parallel |
Sending multiple requests to different actors and waiting for the responses only after all the requests have
been sent is the simplest form of parallel processing and is the focus of this package.
|
| org.agilewiki.jactor.properties |
A table of name/value pairs.
|
| org.agilewiki.jactor.pubsub.actorName |
Actors which include the ActorName component can be named
and added to an ActorRegistry.
|
| org.agilewiki.jactor.pubsub.publisher | |
| org.agilewiki.jactor.pubsub.subscriber | |
| org.agilewiki.jactor.simpleMachine |
You can think of a State Machine as a kind of computer.
|
Copyright © 2012. All Rights Reserved.