| 1 |
On Freitag 12 Februar 2010, Zeerak Waseem wrote: |
| 2 |
> On Fri, 12 Feb 2010 00:03:27 +0100, Volker Armin Hemmann |
| 3 |
> |
| 4 |
> <volkerarmin@××××××××××.com> wrote: |
| 5 |
> > On Donnerstag 11 Februar 2010, Zeerak Waseem wrote: |
| 6 |
> >> On Thu, 11 Feb 2010 23:53:10 +0100, Volker Armin Hemmann |
| 7 |
> >> |
| 8 |
> >> <volkerarmin@××××××××××.com> wrote: |
| 9 |
> >> > On Donnerstag 11 Februar 2010, Zeerak Waseem wrote: |
| 10 |
> >> >> Particularly when your wm can handle all the inter-app |
| 11 |
> >> >> communication that is necessary without dbus. |
| 12 |
> >> > |
| 13 |
> >> > the problem is the WM can NOT handle all the inter-app communication |
| 14 |
> >> > that is |
| 15 |
> >> > needed by a modern desktop environment. Especially, when you have apps |
| 16 |
> >> > that |
| 17 |
> >> > are just frames around building blocks that have to talk to each other |
| 18 |
> >> > (like |
| 19 |
> >> > for example konqueror, that is just a gui to the dolphin, khtml, |
| 20 |
> >> |
| 21 |
> >> konsole, |
| 22 |
> >> |
| 23 |
> >> > gwenview kparts). |
| 24 |
> >> |
| 25 |
> >> But it seems to me, that the apps that need the communication are in |
| 26 |
> >> DE's. |
| 27 |
> >> Which is fine, I just think that if you're choosing a smaller WM |
| 28 |
> >> (Openbox, |
| 29 |
> >> awesome, JWM, etc.), where there isn't a need for an inter-app |
| 30 |
> >> communication that extensive, then it's a bit of an overkill really. |
| 31 |
> > |
| 32 |
> > so how do you propose that a network connection manager tells a broweser |
| 33 |
> > or |
| 34 |
> > mail app that they are offline? |
| 35 |
> > |
| 36 |
> > And don't start with sockets. That will result in a nightmare. dbus is a |
| 37 |
> > clean |
| 38 |
> > solution to a huge problem. Apps have to talk to each other. The only |
| 39 |
> > way to |
| 40 |
> > keep it sane is a standardized IPC daemon like dbus. |
| 41 |
> |
| 42 |
> Well how about something with sockets ;) |
| 43 |
|
| 44 |
because then you need all apps to talk the same 'language'. You also have to |
| 45 |
built in filters into every app to prevent 'malicious' or damaged messages from |
| 46 |
doing harmfull stuff. |
| 47 |
|
| 48 |
Every app. So from a workload, maintenance and security POV - a nightmare. Oh, |
| 49 |
and don't forget the wasted memory and CPU cycles because of all the |
| 50 |
duplicated code. |
| 51 |
|
| 52 |
|
| 53 |
dbus is a clean and simple solution that reduces workload for the devs AND |
| 54 |
resources needed by the system. A win-win scenario. |
| 55 |
|
| 56 |
> |
| 57 |
> Personally, I don't see a big problem in a network connection manager not |
| 58 |
> being able to tell various apps that they don't have a connection to the |
| 59 |
> internet. If you're offline often you will know it, and if not you have |
| 60 |
> something to look into. |
| 61 |
|
| 62 |
oh yeah, it is just a great thing that the mail app constantly tries to reach |
| 63 |
servers and then throws errors. Not like this needs zero cpu cycles and zero |
| 64 |
ram. It is so much worse that the mail app knows that there is nothing to do |
| 65 |
and that it can sleep on... |
| 66 |
|
| 67 |
<sarcasm> |
Archives