Release status.



Hi guys,

I am now keeping a buglist of the blockers for our 0.1 release.  Go to:

	http://nat.org/dashboard

and click on '0.1 bugs' at the top of the page.

The number one issue is:

	http://bugzilla.gnome.org/show_bug.cgi?id=128831

which is that Dashboard seems to stop responding to new cluepackets
after a while.  The reigning theory has been that blocking network
backends are causing the threadpool to fill up, so that no new backend
threads can be created.

One possible solution is to move away from using BeginInvoke in the CPM
and create our own custom thread pools using System.Threading.Thread
directly.  Then, when a new cluepacket comes in we can abort all the
running threads.  I'm not sure how well thread abortion works in Mono,
or how reliable it is; it sounds a bit sketchy.

Nat





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]