TransportRequestHandler is a MessageHandler of RequestMessage messages from Netty’s Channel.
TransportRequestHandler is created exclusively when TransportContext is requested to createChannelHandler.
|
Tip
|
Enable Add the following line to Refer to Logging. |
void processRpcRequest(final RpcRequest req)processRpcRequest…FIXME
|
Note
|
processRpcRequest is used exclusively when TransportRequestHandler is requested to handle a RpcRequest request.
|
void processFetchRequest(final ChunkFetchRequest req)processFetchRequest…FIXME
|
Note
|
processFetchRequest is used exclusively when TransportRequestHandler is requested to handle a ChunkFetchRequest request.
|
void processOneWayMessage(OneWayMessage req)processOneWayMessage…FIXME
|
Note
|
processOneWayMessage is used exclusively when TransportRequestHandler is requested to handle a OneWayMessage request.
|
void processStreamRequest(final StreamRequest req)processStreamRequest…FIXME
|
Note
|
processStreamRequest is used exclusively when TransportRequestHandler is requested to handle a StreamRequest request.
|
void handle(RequestMessage request)|
Note
|
handle is part of MessageHandler Contract to handle messages (aka requests).
|
handle branches off per the type of the input RequestMessage:
-
For
ChunkFetchRequestrequests,handleprocessFetchRequest -
For
RpcRequestrequests,handleprocessRpcRequest -
For
OneWayMessagerequests,handleprocessOneWayMessage -
For
StreamRequestrequests,handleprocessStreamRequest
For unknown requests, handle simply throws a IllegalArgumentException.
Unknown request type: [request]TransportRequestHandler takes the following when created:
-
Netty’s Channel
-
Maximum number of chunks allowed to be transferred at the same time
TransportRequestHandler initializes the internal registries and counters.