[Gtk-sharp-list] Gtk# threading problem?

[Bob Smith]

Yah, but at very least, couldnt you see if the code calling gtk# is secure
and if not, wrap every call.

On 9 Oct 2002, Vladimir Vukicevic wrote:

> On Wed, 2002-10-09 at 20:48, Miguel de Icaza wrote:
> > Bob,
> >
> > > Isnt this extremely dangerious from the standpoint of running applications
> > > securely? If any old app can just spawn off a few threads and call into
> > > gtk# at once, we're in trouble. :)
> > >
> > > While I like the idea of doing this in C, since we're worried about
> > > performance there, the .NET bindings should take care of this stuff so
> > > that we can have a secure environment.
> >
> > I have no idea what you are talking about Bob.
>
> I'm guessing he wants the equivalent of GDK_THREADS_ENTER and
> GDK_THREADS_LEAVE, but for all of gtk.  i.e. have every gtk call, unless
> known safe, explicitly acquire a mutex.  This would, however, be
> absolutely brutal for peformance.
>
> 	- Vlad
>
> --
> Vladimir Vukicevic <vladimir@pobox.com>
>