org.lightwolf

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

PREV PACKAGE NEXT PACKAGE

FRAMES NO FRAMES

Package org.lightwolf

Core classes for flow manipulation and synchronization.

See:
Description

Interface Summary
IMatcher
IProcessListener	A listener for `Process` events.
IRequest	An object that contains a request sent to a flow.

Class Summary
Connection
Continuation	An object that stores a flow's execution context for further resuming.
FileProcess	A process that stores data on a file.
Flow	An execution context similar to that of a thread, but with more capabilities.
FlowData
FlowLocal<T>	An object that stores data associated with a `Flow`.
FlowManager	An object that controls execution of flows by assigning them to actual threads.
IOActivator	An object that activate flows when a NIO channel operation becomes available.
MethodFrame	An internal class invoked by enhanced flow-methods.
Process	An unit of work composed by a set of related flows.
ProcessManager

Exception Summary
AddressAlreadyInUseException
DelayedCallSignal
FlowException	An exception that encapsulates another, thrown by a flow.
FlowInterruptedException
FlowSignal	The root of all signal classes.
FlowSignalException
IllegalReturnValueException
ResumeException
SuspendSignal	A signal indicating that the flow was suspended.

Annotation Types Summary
FlowMethod	Marks a method to execute in the context of a `Flow`.

Core classes for flow manipulation and synchronization.

This package contains the Flow class and the FlowMethod annotation, which are used to build flows in Java. A flow is very similar to a thread:

Each flow have a stack frame, like a thread.
A flow, like a thread, can run Java methods. Such methods can be interpreted but also just-in-time compiled.
Flows can access heap objects. The heap space is the same used by threads. Flows and threads can shared such objects in a transparent way.
Flows can be suspended or interrupted.

The following summarizes the differences between flows and threads:

A flow can be suspended, have its state removed from memory, then restored to memory and then resumed, possibly on another JVM instance or machine.
When a flow is suspended, it does not consume a Java thread, and not even a system thread. This makes flows more friendly to thread-pools.
The Flow is a final class. To create a flow, one must write and call a flow-method.