GNOME Bugzilla – Bug 302719
GroupWise logoutRequest does not appear to be called
Last modified: 2013-07-23 14:37:36 UTC
I can't see the GroupWise logoutRequest. 1. Login to a GroupWise user with Evo. 2. Close down Evo. 3. I observe that a logout request is not called for mail or calendar.
Chen told me that the GroupWise logoutRequest occurs for the mailer when Evo is closed down. I tested and did not see any logout requests. I am also trying to understand when EDS would be closed down to close the calendar/AB. With the getQM calls, doesn't EDS alway remain alive. Meaning that the Calendar/AB connections will never get a logoutRequest.
A logoutRequest would be issued on the Calendar/AB session (and that is just one connection, not two) when e-d-s goes down. Yes, eds (being somewhat like a daemon service) would remain alive as long as atleast one of its calendar/addressbook clients is alive. Besides evolution, the alarm daemon and the panel applets (contact, clock etc.) serve as its clients. When evolution is closed, a logoutRequest should normally be issued only on the mailer session.
It sounds to me like EDS will more than likely not call the GroupWise logout request for AB/Calendar. Why can't you logout and retrieve the new/modified items on startup. I am assumming that the mailer will be doing it this way because it calls the logout request when Evo goes down. In my testing, I did not see the logout request for the mailer when I closed down evo.
confirming the bug.
evolution-groupwise provides connectivity to Novell Groupwise servers. The last stable release of evolution-groupwise was 3.4.2 which took place a year ago. evolution-groupwise is not under active development anymore. It is currently unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.