Hi Patrick, This week I've been going down the path to get the password request working. However, to get the session to even request a password we've got to start a session which is one of the things I've been working on.
One question I've got is when do we go about activating the sessions. I'm assuming this can be done immediately. The approach I'm taking now is to set the session 'active' and emit a status signal as soon as the helper session's up and ready. Thus, the server creates a session and it runs immediately. I've also needed to look at how shutdown is handled in the course of this. From what I can tell there are 2 events that can cause a shutdown request: a signal or a file change. Because we are now dealing with the ideal case that we have no queued sessions & multiple sessions are running concurrently, it doesn't seem to me that we need a ShutdownSession any longer. The shutdown session seemed to be used to get to the head of the queue and prevent any new sessions from starting. I'm going about removing that and just using the m_shutdownRequested flag to disallow starting any additional sessions etc. Now for the actual infoRequest I'm doing the following. When the request is made the helper emits a password request signal and waits. The helper only does one job, so this is fine. The SessionResource in the server receives this signal and creates an InfoRequest. Now we can't wait in the server process because we've got possibly multiple concurrent sessions running. So, I've introduced signal in InfoReq that lets us know when the response is received. This signal is connected to a routine in the SessionResource which passes the result to the session helper who can now carry on its business. I welcome any input as to whether these are all sound assumptions. This code will land very soon. Cheers, Chris _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
