[no subject]
* D-BUS is low-latency because it is designed to avoid round trips and allow
asynchronous operation, much like the X protocol.
* D-BUS is low-overhead 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.
* D-BUS is easy to use because it works in terms of messages rather than byte
streams, and does not require users to understand any complex concepts such
as a new type system or elaborate APIs. Libraries implementing D-BUS may
choose to abstract messages as "method calls"
</quote>
What does "low-latency" mean? Would D-Bus deliver Quality of Service?
What kind QoS is warranted?
Besides, "works in terms of messages" and "uses a binary protocol" are
somewhat controversial, IMO.
If you want low-overhead - youshould send byte streams (not byte streams)
I hope Havoc and other developers backing D-Bus can explain a little bit D-Bus
design goals with more details, so that questions above can be answered.
Greetings,
Vadim
|
| Havoc
--
Best Regards,
Vadim Plessky
SVG Icons * BlueSphere Icons 0.3.0 released
http://svgicons.sourceforge.net
[
Date Prev][Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]