Version 2 will rely solely on explicit state-passing objects instead of the implicit module-level global state of v1, and will thus be threadsafe. An alpha is being actively worked on and this ML will be updated when it's publicized for review/feedback (should be early next month) :) thanks!
On Tue, Aug 25, 2015 at 1:15 PM, Mradul Maheshwari <[email protected]> wrote: > Hi All, > I want to know if there are any plans of making fabric thread safe. Will it > be possible to share those plans. > > My use case is that I dont want to use the globalcache that is maintained > for the connections that are created via fabric. In case the the remote host > closes the connections the global cache still maintains the connection > information. > > To avoid this I plan to create a global cache by per thread. And when the > thread dies the cache is also lost. Is this possible with current > implementation? > > In case the above use case is not solvable, I would also like to try and > contribute this feature back to fabric. Is this welcomed by the maintainers > of fabric. > > -- > Thanks & Regards, > Mradul Maheshwari > > _______________________________________________ > Fab-user mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/fab-user > -- Jeff Forcier Unix sysadmin; Python/Ruby engineer http://bitprophet.org _______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
