Re: [Twisted-Python] Deferred getChild (#3621)

On May 30, 2011, at 6:51 AM, Laurens Van Houtven wrote: > I remember Glyph saying something about how that could potentially > change/break public API. I understand that reservation, but I don't see how > it'd be that bad. Existing code that always immediately returns a resource > would still w

Re: [Twisted-Python] Asynchronous code PEP

On May 30, 2011, at 7:25 AM, Laurens Van Houtven wrote: > Hi! > > I've just been in contact with Jim Fulton, who was previously mentioned in > the context of developing this PEP, and he's okay with us taking over. > > IIUC the PEP involves a few things: > A sane reactor abstraction/interface (

Re: [Twisted-Python] Deferred getChild (#3621)

Right, it's definitely possible to work around this problem using proxy children, but going forward I don't think that's how Twisted *should* behave. (I actually tried this, and nope, it's not exactly pretty :-( ) The reason for that is that that would mean there's two ways to do things. Suppose

Re: [Twisted-Python] Deferred getChild (#3621)

On Monday 30 May 2011, Laurens Van Houtven wrote: > My use case for this is txYoga . Long > story short, it lets you write REST-y webapps. So, you could have > something like: > > http://www.twistedmatrix.com/labs/glyph > > In local jargon, labs is a collection, an

[Twisted-Python] Asynchronous code PEP

Hi! I've just been in contact with Jim Fulton, who was previously mentioned in the context of developing this PEP, and he's okay with us taking over. IIUC the PEP involves a few things: 1. A sane reactor abstraction/interface (although they probably won't like pulling in z.i.I) in the sta

[Twisted-Python] Deferred getChild (#3621)

Hi, I was wondering if anyone had any concrete thoughts about what should happen with IResource.getChild being able to return Deferreds, or, in general, the ability to asynchronously get children of a resource. The ticket for this is #3621 . My use case for this is txYoga