Forum Discussion
Calls from classic asp web pages to custom com+ soap web adaptor sequential/concurrent issue
Hi, I have a classic asp web site which uses a custom com+ app installed on the server to communicate with a custom soap web service. When I use the website installed on a Windows 10 Ent workstatio...
In testing further I now realise that this seems to have nothing to do with the com+ app and everything to do with the fact that IIS is not serving pages from the same client concurrently, which has something to do with session state. As I have classic pages which load content into several embedded iframes, the main page is impacted because these are not being handled concurrently.