Message151303
> The idea is to have access to the current state of the Future using a property instead of calling several methods (done, cancelled, etc.).
I think one point of having methods is that querying is decoupled from implementation. The internal states could for example be finer-grained than what is exposed by the API.
> Also, a history property that returns a list of Event(state, timestamp) objects is written, the list stores the timestamp every time the state of a future changes.
Uh, what is the use case exactly? |
|
Date |
User |
Action |
Args |
2012-01-15 23:04:50 | pitrou | set | recipients:
+ pitrou, bquinlan, jjdominguezm |
2012-01-15 23:04:50 | pitrou | set | messageid: <1326668690.72.0.343029110531.issue13785@psf.upfronthosting.co.za> |
2012-01-15 23:04:50 | pitrou | link | issue13785 messages |
2012-01-15 23:04:49 | pitrou | create | |
|