Module org.neo4j.driver
Class LegacyPullAllResponseHandler
java.lang.Object
org.neo4j.driver.internal.handlers.LegacyPullAllResponseHandler
- All Implemented Interfaces:
PullAllResponseHandler,ResponseHandler
This is the Pull All response handler that handles pull all messages in Bolt v3 and previous protocol versions.
-
Field Summary
Fields -
Constructor Summary
ConstructorsConstructorDescriptionLegacyPullAllResponseHandler(Query query, RunResponseHandler runResponseHandler, Connection connection, MetadataExtractor metadataExtractor, PullResponseCompletionListener completionListener) -
Method Summary
Modifier and TypeMethodDescriptionbooleanTells whether this response handler is able to manage auto-read of the underlying connection usingConnection.enableAutoRead()andConnection.disableAutoRead().voidIf this response handler is able to manage auto-read of the underlying connection, then this method signals it to stop changing auto-read setting for the connection.<T> CompletionStage<List<T>>voidvoidvoidvoid
-
Field Details
-
metadataExtractor
-
connection
-
-
Constructor Details
-
LegacyPullAllResponseHandler
public LegacyPullAllResponseHandler(Query query, RunResponseHandler runResponseHandler, Connection connection, MetadataExtractor metadataExtractor, PullResponseCompletionListener completionListener)
-
-
Method Details
-
canManageAutoRead
public boolean canManageAutoRead()Description copied from interface:ResponseHandlerTells whether this response handler is able to manage auto-read of the underlying connection usingConnection.enableAutoRead()andConnection.disableAutoRead().Implementations can use auto-read management to apply network-level backpressure when receiving a stream of records. There should only be a single such handler active for a connection at one point in time. Otherwise, handlers can interfere and turn on/off auto-read racing with each other.
InboundMessageDispatcheris responsible for tracking these handlers and disabling auto-read management to maintain just a single auto-read managing handler per connection.- Specified by:
canManageAutoReadin interfaceResponseHandler
-
onSuccess
- Specified by:
onSuccessin interfaceResponseHandler
-
onFailure
- Specified by:
onFailurein interfaceResponseHandler
-
onRecord
- Specified by:
onRecordin interfaceResponseHandler
-
disableAutoReadManagement
public void disableAutoReadManagement()Description copied from interface:ResponseHandlerIf this response handler is able to manage auto-read of the underlying connection, then this method signals it to stop changing auto-read setting for the connection.- Specified by:
disableAutoReadManagementin interfaceResponseHandler
-
peekAsync
- Specified by:
peekAsyncin interfacePullAllResponseHandler
-
nextAsync
- Specified by:
nextAsyncin interfacePullAllResponseHandler
-
consumeAsync
- Specified by:
consumeAsyncin interfacePullAllResponseHandler
-
listAsync
- Specified by:
listAsyncin interfacePullAllResponseHandler
-
prePopulateRecords
public void prePopulateRecords()- Specified by:
prePopulateRecordsin interfacePullAllResponseHandler
-
pullAllFailureAsync
- Specified by:
pullAllFailureAsyncin interfacePullAllResponseHandler
-