Two questions: 1 - I create a session in one process and context save it. In another process, I flushcontext, and it flushes the saved context. I would not have expected a process to be able to flush another process' context. Is this working as designed? 2 - This is a more basic question. One process creates a session, context saves it, and then exits - maliciously or due to a bug. This saved session will be there until eventually startauthsession fails due to the context gap issue. Or an errant process starts and context saves 64 sessions, which blocks any process from starting a session. The new process can recover by picking some session and flushing it (which works due to #1) but that breaks another process. What I expected - perhaps worth discussing: Save and load context would be used solely by the resource manager to swap. The RM, upon detecting a close() or an exiting process, would flush all resources associated with that process, including active sessions. (The Windows resource manager blocks context save and load.)
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
