Hi, --On Wednesday, February 27, 2002 8:20 AM -0700 "Alec H. Peterson" <[EMAIL PROTECTED]> wrote:
|> For improved performance, Cyrus tends to cache seen state changes |> until the connection SELECTs some other mailbox. Thus the other |> connection isn't changing its count. |> |> I don't have time to go looking through the code to see where this |> behavior can be modified; I don't think it would be all that difficult |> but the performance impact could be substantial. | | Well if you could point me in the direction of where said caching takes | place I'd be happy to play with it myself and report back. The important thing to note is a recent change in our connection handling that keeps a connection active for a short while after the user closes a mailbox window, so that if they open another mailbox soon after, the connection can be reused, avoiding the overhead of connection setup and authentication. In this case we use the UNSELECT command on the previous mailbox to effectively 'close' it. That command ought to invalidate the cache, as should the CLOSE command, which may be used in other situations. -- Cyrus Daboo
