mirror of
https://gitlab.freedesktop.org/dbus/dbus.git
synced 2026-05-08 10:18:01 +02:00
Remove obscure "low-latency" parts in the introduction of spec
According to Wikipedia http://en.wikipedia.org/wiki/Latency_%28engineering%29#Packet-switched_networks latency means "the time from the source sending a packet to the destination receiving it". Therefore, latency is unrelated to whether the operation is asynchronous or synchronous. And also unrelated to whether it's one-way or round-trip. Latency exists for asynchronous and one-way transfer, because for current DBus implementations we need at least one context switch to transfer each message from the sender process to the receiver process. Emphasizing D-Bus is low-latency could encourage user to abuse/misuse the system. Mail disscusion: http://lists.freedesktop.org/archives/dbus/2013-May/015665.html Bug: https://bugs.freedesktop.org/show_bug.cgi?id=65141 Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
This commit is contained in:
parent
c627c4119f
commit
8d2536e023
1 changed files with 4 additions and 9 deletions
|
|
@ -175,23 +175,18 @@
|
|||
<sect1 id="introduction">
|
||||
<title>Introduction</title>
|
||||
<para>
|
||||
D-Bus is a system for low-latency, low-overhead, easy to use
|
||||
D-Bus is a system for low-overhead, easy to use
|
||||
interprocess communication (IPC). In more detail:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
D-Bus is <emphasis>low-latency</emphasis> because it is designed
|
||||
to avoid round trips and allow asynchronous operation, much like
|
||||
the X protocol.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
D-Bus is <emphasis>low-overhead</emphasis> because it uses a
|
||||
binary protocol, and does not have to convert to and from a text
|
||||
format such as XML. Because D-Bus is intended for potentially
|
||||
high-resolution same-machine IPC, not primarily for Internet IPC,
|
||||
this is an interesting optimization.
|
||||
this is an interesting optimization. D-Bus is also designed to
|
||||
avoid round trips and allow asynchronous operation, much like
|
||||
the X protocol.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue