On Feb 8, 2011, at 8:58 AM, Tomaz Muraus wrote: > On Tue, Feb 8, 2011 at 2:57 PM, Schwartz, Philip Marc (LNG-BCT) < > [email protected]> wrote: > >> I would also vote -1 to twisted. But 0 to async. I am for async to a point >> as long as it is setup as a per instance option for the user. >> > > Yes, that is how I have envisioned it. I probably should have explained it > better in my original post. > > The change should be non-disruptive and the Twisted dependency should be > optional (basically it would be totally up to the user if he wants to use > async API or not). > > And like Paul has pointed out above, refactoring a library might not be a > bad idea, since we will need to split and refactor some of the existing > methods and this will make testing (among other things) easier.
All this being said -- Paul, where is your node.js port of Libcloud? ;) Cheers, Jerry
