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 64532 - Move to low-latency custom protocol
Move to low-latency custom protocol
Status: RESOLVED NOTABUG
Product: GConf
Classification: Deprecated
Component: gconf
unspecified
Other Linux
: Normal enhancement
: future
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-11-14 04:02 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Havoc Pennington 2001-11-14 04:02:11 UTC
GConf's current use of CORBA for IPC is suboptimal, for several reasons. 
Most importantly, unless we move all IPC into a separate thread, it
guarantees average somewhat-too-high latency, and worst-case unbounded
latency. Also, even the current use of "oneway" can't 100% guarantee that
we won't block, while we should really have that guarantee especially for
the daemon. The current IDL is an unextensible mess, and making it
extensible would involve stripping it down to send_extensible_text_blob()
as a method, which is identical to a custom protocol.

I would move instead to a protocol like the X protocol, which is designed
to avoid round trips. Alternatively, perhaps a reworking in terms of ACAP
with extensions would be appropriate.

A protocol would also encourage wider adoption outside of GNOME.

In any case, a long-term project to think about.
Comment 1 Havoc Pennington 2003-03-06 03:19:15 UTC
Not keeping this open, not useful to track in bugzilla really.