Hi All !
My stateful BSP Application uses a copy of session_buffered_frame.htm as entry point. When the browser window or tab is closed this makes sure that all user sessions are closed properly. This works fine so far.
Unfortunately I have users opening the application simultaneous in multiple browser tabs confusing the session context. Using the sap-syscmd=nocookie parameter makes the trick in this case. It creates separate sessions for each instance of the BSP application.
The problem is, that the session cleanup with session_buffered_frame.htm seems not to be working with sap-syscmd=nocookie. All user sessions remain after closing the tabs or the browser window 
=== EXAMPLE ===
Open /bc/bsp/sap/system/session_buffered_frame.htm in several browser tabs. You will see only one session im SM04. When closing one of the tabs, this session is ended.
Now call /bc/bsp/sap/system/session_buffered_frame.htm?sap-syscmd=nocookie in two tabs and you will see separate sessions in SM04. When closing the tabs, nothing is cleaned up ....
================
Is there a way to change the behavior of session_buffered_frame.htm to clean up nocookie sessions? I should mention that because of the structure of my application, I do know what the session-ID will be BEFORE calling the session_buffered_frame.htm ! Maybe I could change the onUnload-URL to explicitly kill this session ? Alternatively can I prevent the user from opening the application in a second tab at all?
Thanks for Reading !
Tobias
P.S: Helpful hints will be rewarded with a beer on TecED in Berlin next week 