Linked by Thom Holwerda on Sat 24th Nov 2007 23:31 UTC
Gnome "The GNOME Foundation has issued a statement in response to recent accusations that it has been supporting the acceptance of Microsoft's Office Open XML format as an ECMA standard at the expense of the Open Document Format, the open standard used by OpenOffice.org, KOffice and other free software office applications. However, whether the statement's attempt at logical rebuttal will do anything to reduce the emotions or altruism behind the criticisms is anybody's guess."
Thread beginning with comment 286873
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: ...
by anda_skoa on Mon 26th Nov 2007 11:13 UTC in reply to "RE[6]: ..."
anda_skoa
Member since:
2005-07-07

Well, try to fix a mess with another mess like DCOP is ridiculos.


No, since it is less a mess than CORBA for the things it was needed for, it is an improvement.

D-Bus takes the same principles and expands the scope, e.g. system bus.
Again an improvement.

We tend to call this succession of improvements progress and the staying at worst solution stagnation.

Since in your opinion seems to be that the direction is reversed, i.e. D-Bus is worse than CORBA for the needs of desktop IPC, you can of course call it a regression. You probably won't get a lot of followers though

Reply Parent Score: 5

RE[8]: ...
by Hiev on Mon 26th Nov 2007 14:20 in reply to "RE[7]: ..."
Hiev Member since:
2005-09-27

I don't say that DBUS is not better than Corba because it is, My point is that say DBUS borrowed most of its architecture from DCOP is false and ridiculous because DCOP was a mess also, better than corba but still a mess.

Edited 2007-11-26 14:20

Reply Parent Score: 0

RE[9]: ...
by anda_skoa on Mon 26th Nov 2007 20:42 in reply to "RE[8]: ..."
anda_skoa Member since:
2005-07-07

My point is that say DBUS borrowed most of its architecture from DCOP is false...


I am sorry, but it isn't.

In both cases there is a daemon process which acts as a message switch, i.e. clients send message to it and it then relays it to the correct receipient.

In both cases this daemon also keeps track of who is connected and handles name registration.

In both cases a method call is addressed to an object inside a specific receipient.

In both cases connected applications can send signals which will be "broadcasted" to all other applications.

Reply Parent Score: 4