Examples of Fiber

co.paralleluniverse.fibers.Fiber
A lightweight thread.
There are two ways to create a new fiber: either subclass the {@code Fiber} class and override the {@code run} method,or pass the code to be executed in the fiber as the {@code target} parameter to the constructor. All in all, the Fiber APIresembles the {@link Thread} class in many ways.
A fiber runs inside a ForkJoinPool.
A Fiber can be serialized if it's not running and all involved classes and data types are also {@link Serializable}.
A new Fiber occupies under 400 bytes of memory (when using the default stack size, and compressed OOPs are turned on, as they are by default). @param < V> The type of the fiber's result value. Should be set to {@link Void} if no value is to be returned by the fiber. @author pron
com.sun.xml.internal.ws.api.pipe.Fiber
User-level thread. Represents the execution of one request/response processing.
JAX-WS RI is capable of running a large number of request/response concurrently by using a relatively small number of threads. This is made possible by utilizing a {@link Fiber} — a user-level thread that gets created for each request/responseprocessing.
A fiber remembers where in the pipeline the processing is at, what needs to be executed on the way out (when processing response), and other additional information specific to the execution of a particular request/response.
Suspend/Resume

Fiber can be {@link NextAction#suspend() suspended} by a {@link Tube}. When a fiber is suspended, it will be kept on the side until it is {@link #resume(Packet) resumed}. This allows threads to go execute other runnable fibers, allowing efficient utilization of smaller number of threads.
Context-switch Interception

{@link FiberContextSwitchInterceptor} allows {@link Tube}s and {@link Adapter}s to perform additional processing every time a thread starts running a fiber and stops running it.
Context ClassLoader

Just like thread, a fiber has a context class loader (CCL.) A fiber's CCL becomes the thread's CCL when it's executing the fiber. The original CCL of the thread will be restored when the thread leaves the fiber execution.
Debugging Aid

Because {@link Fiber} doesn't keep much in the call stack, and instead use{@link #conts} to store the continuation, debugging fiber related activitiescould be harder.
Setting the {@link #LOGGER} for FINE would give you basic start/stop/resume/suspendlevel logging. Using FINER would cause more detailed logging, which includes what tubes are executed in what order and how they behaved.
When you debug the server side, consider setting {@link Fiber#serializeExecution}to true, so that execution of fibers are serialized. Debugging a server with more than one running threads is very tricky, and this switch will prevent that. This can be also enabled by setting the system property on. See the source code. @author Kohsuke Kawaguchi @author Jitendra Kotamraju
com.sun.xml.ws.api.pipe.Fiber
User-level thread. Represents the execution of one request/response processing.
JAX-WS RI is capable of running a large number of request/response concurrently by using a relatively small number of threads. This is made possible by utilizing a {@link Fiber} — a user-level thread that gets created for each request/responseprocessing.
A fiber remembers where in the pipeline the processing is at, what needs to be executed on the way out (when processing response), and other additional information specific to the execution of a particular request/response.
Suspend/Resume

Fiber can be {@link NextAction#suspend() suspended} by a {@link Tube}. When a fiber is suspended, it will be kept on the side until it is {@link #resume(Packet) resumed}. This allows threads to go execute other runnable fibers, allowing efficient utilization of smaller number of threads.
Context-switch Interception

{@link FiberContextSwitchInterceptor} allows {@link Tube}s and {@link Adapter}s to perform additional processing every time a thread starts running a fiber and stops running it.
Context ClassLoader

Just like thread, a fiber has a context class loader (CCL.) A fiber's CCL becomes the thread's CCL when it's executing the fiber. The original CCL of the thread will be restored when the thread leaves the fiber execution.
Debugging Aid

Because {@link Fiber} doesn't keep much in the call stack, and instead use{@link #conts} to store the continuation, debugging fiber related activitiescould be harder.
Setting the {@link #LOGGER} for FINE would give you basic start/stop/resume/suspendlevel logging. Using FINER would cause more detailed logging, which includes what tubes are executed in what order and how they behaved.
When you debug the server side, consider setting {@link Fiber#serializeExecution}to true, so that execution of fibers are serialized. Debugging a server with more than one running threads is very tricky, and this switch will prevent that. This can be also enabled by setting the system property on. See the source code. @author Kohsuke Kawaguchi @author Jitendra Kotamraju
org.jetlang.fibers.Fiber

Examples of org.jetlang.fibers.Fiber


    public Downloader() {
        PoolFiberFactory f = new PoolFiberFactory(pool);
        //subscribe multiple fibers for parallel execution
        for(int i = 0, numThreads = 10; i < numThreads; i++) {
            Fiber fiber = f.create();
            fiber.start();
            fibers.add(fiber);
            channel.subscribe(fiber, new DownloadCallback());
        }
    }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of Fiber

Suspend/Resume

Context-switch Interception

Context ClassLoader

Debugging Aid

Suspend/Resume

Context-switch Interception

Context ClassLoader

Debugging Aid

Examples of org.jetlang.fibers.Fiber