Closed GoogleCodeExporter closed 9 years ago
So after talking to Nick Coghlan & Jesse Noller on the mailing list it has been
determined the first API change was ill-designed so I started over from scratch.
This new design creates a singleton registration/tracking class. This new
singleton
class allows several things
1) Removal of all the global scoped tracking/cleanup code that was required for
each
executor
2) 3rd parties can register their own executor with the system
3) a Factory is used to create new executors based on their registered name.
The registration/factory system is NOT required to be used, it is there for
convenience, but the tracking/cleanup functionality of the new class is
required to
be used within an executor itself. This ensures all executors are tracked and
cleanup
to prevent memory leaks.
On the mailing list both Jean-Paul & Antoine Pitrou are +1 for the idea, but
have not
looked at the patch yet
Original comment by digitalx...@gmail.com
on 9 Mar 2010 at 9:27
Attachments:
I'm looking at the patch now but it will take me a while.
Original comment by brian.qu...@gmail.com
on 19 Mar 2010 at 10:39
Hi,
I'm incorporated the windows fixes (thanks!) but I don't agree with the
registration API changes.
Cheers,
Brian
Original comment by Dublin...@gmail.com
on 21 May 2010 at 1:22
Original comment by brian.qu...@gmail.com
on 14 Nov 2010 at 3:49
Original issue reported on code.google.com by
digitalx...@gmail.com
on 7 Mar 2010 at 3:06