-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to properly test and close a connexion ? #48
Comments
See inline On Nov 26, 2013, at 12:59 PM, Benjamin Ooghe-Tabanou notifications@github.com wrote:
Hard to say. I had similar problems back in 2009-2010 when I gave up using MongoDB.
You can open as many new connections as you need without closing existing ones. To terminate a connection (or pool) there's the
The
|
Thanks a lot, I understand better the Lazy part now. I saw the other issue regarding Auth with Lazy and Pools though and since I'm using auth it looks like I'm limited to the classic connexion. |
I still don't understand why you want to close the connection and reconnecting later. And yes, I'm no longer using mongo and thus not actively maintaining this lib for about 2-3 years. On Nov 27, 2013, at 10:08 AM, Benjamin Ooghe-Tabanou notifications@github.com wrote:
|
This is the fork that I have been using: https://github.com/chergert/txmongo. I have been contributing here and there, and might be able to help with some issues. |
And thanks @fiorix for getting it all started ;) |
My pleasure. I really enjoyed working on it back in the days. On Nov 27, 2013, at 11:07 AM, Trenton Broughton notifications@github.com wrote:
|
@fiorix: Since I'm using Auth I apparently have no choice but to use the regular connexion instead of a pool. Which means I need to open multiple ones if I want multiple db operations to happen simultaneously, which means I need to make sure I'm not opening too many and therefore need to close some of them. And in any case the closing of my daemon should use the disconnect at least for clean exit. @trenton42: Great thanks, I'll take a look at the commits history to see what you improved. Any chance you worked on the auth issue with the other connexion types maybe? |
Hi,
I'm using txmongo in an environment with a lot of running parallel tasks (twitter and rss collection mostly) and was wondering which best practice would be recommended to use txmongo :
The text was updated successfully, but these errors were encountered: