org.jredis.ri.alphazero.connection

Class ChunkedPipelineConnection.ResponseHandler

java.lang.Object

org.jredis.ri.alphazero.connection.ChunkedPipelineConnection.ResponseHandler

All Implemented Interfaces:

java.lang.Runnable, Connection.Listener

Enclosing class:

ChunkedPipelineConnection

public final class ChunkedPipelineConnection.ResponseHandler
extends java.lang.Object
implements java.lang.Runnable, Connection.Listener

Provides the response processing logic as a Runnable.

TODD: Needs to have a more regulated operating cycle. Right now its just infinite loop until something goes boom. Not good.

Since:

alpha.0

Version:

alpha.0, Oct 18, 2009

Field Summary

Fields

Modifier and Type	Field and Description
private java.util.concurrent.atomic.AtomicBoolean	alive_flag
private java.util.concurrent.atomic.AtomicReference<java.lang.Thread>	thread
private boolean	work_flag

Constructor Summary

Constructors

Constructor and Description
ResponseHandler() Adds self to the listeners of the enclosing Connection instance.

Method Summary

Modifier and Type	Method and Description
void	onEvent(Connection.Event event)
void	run() Keeps processing the PendingRequests in the pending Queue until a QUIT is encountered in the pending queue.
private void	shutdownHandler()
private void	stopHandler()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

work_flag

private volatile boolean work_flag

alive_flag

private final java.util.concurrent.atomic.AtomicBoolean alive_flag

thread

private final java.util.concurrent.atomic.AtomicReference<java.lang.Thread> thread

Constructor Detail

ResponseHandler

public ResponseHandler()

Adds self to the listeners of the enclosing Connection instance.

Method Detail

run

public void run()

Keeps processing the PendingRequests in the pending Queue until a QUIT is encountered in the pending queue. Thread will stop after processing the QUIT response (which is expected to be a VirtualResponse.

TODO: not entirely clear what is the best way to handle exceptions.

TODO: socket Reconnect in the context of pipelining is non-trivial, and maybe not even practically possible. (e.g. request n is sent but pipe breaks on some m (m!=n) response. non trivial. Perhaps its best to assume broken connection means faulted server, specially given the fact that a pipeline has a heartbeat so the issue can not be timeout.

Specified by:

run in interface java.lang.Runnable

stopHandler

private final void stopHandler()

shutdownHandler

private final void shutdownHandler()

onEvent

public void onEvent(Connection.Event event)

Specified by:

onEvent in interface Connection.Listener

See Also:

Connection.Listener.onEvent(org.jredis.connector.Connection.Event)