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

2011-05-30 Thread Glyph Lefkowitz
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] Deferred getChild (#3621)

2011-05-30 Thread Laurens Van Houtven
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)

2011-05-30 Thread Maarten ter Huurne
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] Deferred getChild (#3621)

2011-05-30 Thread Laurens Van Houtven
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