On Jan 19, 2011, at 11:06 AM, ron_m wrote: > There is another subtle problem. If the file close is not done after the > unlock which is how it works now then the file is still open. It is not > possible to get the exclusive lock in session.connect() until the file is > closed so the second request remains blocked.
Although session.forget(response) seems to work as expected.
