[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Session management questions
From:       Waldo Bastian <bastian () suse ! de>
Date:       2000-04-15 22:42:56
[Download RAW message or body]

Hiya,

I try to understand how session management works. Please correct me if my 
assumptions are wrong.

I assume that applications started before the session manager can not connect 
to the session manager and as a result will not be session managed. If an 
application wants to be managed by session management, it needs to connect to 
the session manager in the QApplication constructor.

Looking at startkde this means that e.g. kdestop, kded and kicker are not 
managed. How does the session manager handle these applications? Does it just 
ignore them?

There are applications that should not be managed by session management, 
either because they might be started before the session manager is active, or 
because they should not be restarted anyway. kapp->disableSessionManagement() 
prevents the application from being restarted by session management but it 
doesn't prevent the application from making a connection with the session 
manager. Would it make sense to prevent certain applications from connecting 
to the session manager by clearing the SESSION_MANAGER environment var before 
calling the QApplication constructor? Think for example about io-slaves.

Does it make sense at all to connect to the session manager if an application 
has its GUI disabled?

Cheers,
Waldo

[prev in list] [next in list] [prev in thread] [next in thread]