We're not sure about what OP has done, but if there is ever anything lacking in TxMongo... please open an issue/ticket with us over at: https://github.com/twisted/txmongo Cheers, Bret On Wed, Oct 7, 2015 at 8:18 PM, Jonathan Vanasco <twisted-python@2xlp.com> wrote:
On Dec 21, 2014, at 4:05 PM, Clayton Daley 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.
I know thread is a bit old, but I'm wondering if the OP ended up using callInThread or not , and if there were any issues.
I started working on a txmongo solution to offload some storage, but then realized I was already in a deferred thread (to handle blocking operations) and i probably should be using pymongo.
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python