Closed zachkinstner closed 11 years ago
See related discussion that RexConnect won't need to manually handle sessions anymore:
The intention is to make RexsterClient session aware for next release, which should eliminate you having to set those properties manually.
Session.Close acts correctly on the RexConnect side, but I noticed the Rexster Server thread counts increasing without bound.