Re: Little Summary of "Daemon for managing dialup internetconnections"

[Waldo Bastian <bastian ens ascom ch>]

Matt Koss wrote:
> 
> Hello,
> 
> as I thought more about this, I came to this conclusion :
> 
> Basically I wanted to make a signal / slot stuff for informing
> apps about the connection and additionally to have a possibility 
> to request / close connection.
> 
> Naturally I got the idea of doing this a CORBA way.
> But even if I hope, that the current MICO bloat situation will 
> be solved, the CORBA approach in this simple task will still
> have more overhead then the approach I want to propose now.
> Also, as we heard, the GNOME people will not use CORBA for this, 
> so the common IDL is not needed.
> It's a little pity, because this way all network apps could share
> the same framework for getting the connection information 
> ( imagine GNOME mail client in KDE ).
> 
> The proposed approach :
> -------------------
> We can simply create a wrapper around NetMgr, let's say a class
> called KNetMgr, which would use NetMgr methods to query a 
> connection watcher, and emit the appropriate signals. KDE apps 
> would then have to create an instance of this class and connect 
> the signals to custom slots.
> 
> For permanent connection would KNetMgr simply not connect to a
> NetMgr at all and never emit signal "disconnected".
> 
> This general class is needed, because app should not have to keep
> the information about the type of connection.

Good approach. I still think a common IDL with GNOME is wanted.
This can be folded in our access library to KNetMgr in a later
stage though.

However, the functionality of our signal/slot interface
should match the functionality of any future common IDL. Therefor
it would be very nice if such an IDL could be agreed upon now.
Even if it isn't used right away.

Cheers,
Waldo Bastian
-- 
KDE, A New Millennium, A New Desktop                      http://www.kde.org