Jason Tackaberry wrote:
> On Fri, 2008-01-11 at 21:08 +0100, Dirk Meyer wrote:
>> >     try:
>> >        do_callback()
>> >     except Exception, exc:
>> >       self.signals['exception'].emit(exc.__class__, exc, sys.exc_traceback)
>> 
>> We should make sure not tp break too much by adding this.
>
> I can fix the spots in kaa if you take care of freevo. :)  Duncan
> probably isn't using this yet in 1.x.

OK. So let us break the API and be sure we do it right this time :)

> While we're breaking stuff, we should look at unifying the API for async
> status/exception handling between Thread and InProgress.  They both
> essentially serve the same purpose: perform some task in the
> "background" (for certain definitions of background) and return either
> the status or an exception asynchronously.

For Thread and InProgress? They ARE different. Thread is something you
start, just like Process. So these two should be similar. InProgress
is a way of telling you that something eeds more time. I like the idea
of InProgress beeing a Signal, not having one. A Thread on the other
hand is not in progress / running if you create it, you have to
start() it. So start should return an InProgress object. The same for
Process.


Dischi

-- 
Save time... see it my way.

Attachment: pgpoyAiZlyhrU.pgp
Description: PGP signature

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to