I have an Active Server Page app in a browser (IE only) that allows users to launch other apps that are loaded in a seperate window using window.open.
The first instance of a newly launched app works fine. When I try to launch an additional instance of the app, connected to a different data source, the new instance of the app ends up using the same session the first one uses. The affect is that the 2nd, 3rd, 4th, etc.. instance are all connected to the same session and hence the same data source the first instance is connected to.
I know that the HTTP header COOKIE contains multiple ASP session IDs and that the first one is associated with the initial app instance launched.
There must be a way aound this short of writing an ISAPI filter that removes the duplicate ASP session IDs.
Any ideas out there... ?
The first instance of a newly launched app works fine. When I try to launch an additional instance of the app, connected to a different data source, the new instance of the app ends up using the same session the first one uses. The affect is that the 2nd, 3rd, 4th, etc.. instance are all connected to the same session and hence the same data source the first instance is connected to.
I know that the HTTP header COOKIE contains multiple ASP session IDs and that the first one is associated with the initial app instance launched.
There must be a way aound this short of writing an ISAPI filter that removes the duplicate ASP session IDs.
Any ideas out there... ?