I'm fine with all items in the Graph hierarchy implementing AutoCloseable (including GraphTraversal). I'm not sure what the implementation would look like though and what it would do. Perhaps I'll take a look at ResourceIterator from Neo4j. If we go with the idea that the user is responsible for properly closing things and close() on each component works in this independent fashion, then we can fire up a separate discussion for what close() on GraphTraversal means (and each item in the Graph hierarchy). Sounds like you're in favor of this approach - i guess we'll see if anyone else has other opinions.
On Wed, Oct 7, 2015 at 8:34 AM, pieter-gmail <[email protected]> wrote: > Ok, how about making GraphTraversal implement AutoCloseable? > > Thanks > Pieter > > On 07/10/2015 14:28, Stephen Mallette wrote: > > n I think the best approach is to leave it to users to close() > > resources properly and keep document it as a convention. So Option 2 > from > > my initial post in this > >
