On Do, 2010-09-16 at 21:10 +0100, Frederik Elwert wrote: > From Genesis’ side, I could catch the exceptions and ignore them (i.e., > act as I did before the new methods were introduced). Should work, but > maybe is not really pretty. Another idea would be to allow other clients > to Attach() to sessions to prevent them from terminating before they are > dealt with.
That *is* already allowed :-) Whether it works is a different question, but it should. > But I don’t know if this is really reasonable. I think it is. You still have a race condition, though. The Attach() method itself may arrive too late. In that case it seems reasonable to me to catch the exception and ignore the session. I could also introduce a delayed clean up of completed sessions. For example, keep them around 1 minute after the last client has detached, just in case that someone is still interested in the session's attributes. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
