Skip to content

Commit a1a1db7

Browse files
Update modules/ROOT/pages/extending-neo4j/unmanaged-extensions.adoc
1 parent bbf7e41 commit a1a1db7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/ROOT/pages/extending-neo4j/unmanaged-extensions.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ When writing unmanaged extensions, you have greater control over the amount of m
102102
If you keep too much state around, it can lead to more frequent full Garbage Collection and subsequent unresponsiveness by the Neo4j server.
103103

104104
A common way that state can increase, is the creation of JSON objects to represent the result of a query, which is then sent back to your application.
105-
Neo4j's Transactional Cypher HTTP endpoint (see link:{neo4j-docs-base-uri}/http-api/current/actions[HTTP API Docs -> transactional Cypher endpoint]) streams responses back to the client.
105+
Neo4j's HTTP endpoint (see link:{neo4j-docs-base-uri}/http-api/current/transactions[HTTP API Docs -> Run transactions]) streams responses back to the client.
106106
For example, the following unmanaged extension streams an array of a person's colleagues:
107107

108108
//https://github.com/neo4j/neo4j-documentation/blob/dev/server-examples/src/main/java/org/neo4j/examples/server/unmanaged/ColleaguesResource.java

0 commit comments

Comments
 (0)