After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 647746 - The GSocketService documentation is incomplete.
The GSocketService documentation is incomplete.
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gio
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-04-14 08:18 UTC by mabdullah
Modified: 2011-04-20 15:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mabdullah 2011-04-14 08:18:12 UTC
The current documentation for GSocketService's incoming signal notes:

The ::incoming signal is emitted when a new incoming connection to service needs to be handled. The handler must initiate the handling of connection, but may not block; in essence, asynchronous operations must be used. 

Need to update this to reflect the fact that the user needs to do g_object_ref() to do anything meaningful with this connection (e.g. send/receive data) from a different thread. Currently as soon as the signal handler returns, the connection gets dropped.
Comment 1 Dan Winship 2011-04-20 15:27:37 UTC
+   * @connection will be unreffed once the signal handler returns, so
+   * you need to ref it yourself if you are planning to use it.