2007/5/29, Michael Hutchinson <[EMAIL PROTECTED]>:
An interesting post on thread safety in java-gnome, especially in the light of recent discussions about the global GTK lock in GTK#: http://research.operationaldynamics.com/blogs/andrew/software/java-gnome/thread-safety-for-java.html
I've read this post too and seems very interesting. I see no obvious reason why it wouldn't be possible to do this in
GTK#, though it may be worth waiting for ReaderWriterLockSlim: http://www.bluebytesoftware.com/blog/PermaLink,guid,c4ea3d6d-190a-48f8-a677-44a438d8386b.aspx Loss of performance may be an issue too, I guess, but it might be worth it for a thread-safe toolkit.
I think it does worth it, in fact, many apps end locking threads more than needed to prevent possible calls from threads... so this slowness penalty is already there anyway. Ideas and comments? Could we have both thread-safe and by-hand-thread-safe (as now it is) builds at the same time? Or it would be too complicated to maintain both? --
Michael Hutchinson http://mjhutchinson.com _______________________________________________ Gtk-sharp-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
_______________________________________________ Gtk-sharp-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
