Re: GObject exposure

[Tristan Van Berkom <tvb gnome org>]

Philip Kovacs wrote:
[...]
> Maybe I am making more out of this than need be.   I have implemented thread-
> safety in my api's; I require glib>=2.8 for thread-safe g_object_[un]ref used
> internally; all of my gobject properties are construct only/write only; and
> the user cannot subclass my objects using the public headers I provide.

I certainly believe you are (making more out of this than need be)

  - Getting/Setting object properties will only happen in the thread that
    the api user is calling your api from
  - If the user is using threads, its up to the user to protect all shared
    data anyway (including your object)
  - If your signals are emitted only from the thread that your user is accessing
    your api in, then the user wont execute accidentally in one of your worker
    threads

Whether or not you chose to provide signals and properties in your initial api;
hiding the possibility of using the GObject api will only limit your api without
adding any kind of extra security.

Cheers,
                  -Tristan