On Tue, Dec 30, 2014 at 5:50 PM, bret curtis firstname.lastname@example.org wrote:
On Tue, Dec 23, 2014 at 7:51 AM, Gelin Yan email@example.com wrote:
On Mon, Dec 22, 2014 at 5:05 AM, Clayton Daley firstname.lastname@example.org wrote:
Are there any major disadvantages of using pymongo with callInThread instead of txmongo? I'd like to take advantage of some newer features in pymongo (unfortunately not available in txmongo) and it's certainly easier to maintain feature parity using callInThread.
Txmongo has been inactive for a while so I suggest using pymongo &
twisted thread pool. I have been using them for a couple of years and they work quite well.
just wanted to drop in and say that txmongo isn't dead. We (Amplidata) just recently sent a merge request to add SSL (authentication/encryption) support that Alexandre will review after the holidays. While Alexandre isn't currently developing txmongo, he does review and accept pull requests. So while the community is small, it is still alive.
Amplidata (the company I work for) has also expressed an interest in getting txmongo up to speed with PyMongo, similar in how we got Ldaptor and its myriad forks to converge and development happening again.
Is there any interest in seeing txmongo be developed further? What are some of the pain points that people would rather defer to thread PyMongo instead of using async txmongo?
I am glad to know txmongo is still here. I used it several times a few years ago and was impressed by its speed (twice faster than pymongo & thread pool).
I hope txmongo can support the latest GEO index & replication.