M
Max Metral
I have an application that has a web interface but also provides a direct
TCP interface for some older systems. In IIS5, I used to just spawn a
thread in Application_Start and clean it up when the app ended, and it
seemed to work fine. In IIS6 (winxp pro dev for a target of win2k3
production), it seems to be more aggressive about cleaning up apps and
generally have odd behavior when I spawn threads.
Am I doing something really wrong here? Should I be remoting everything
into a service and just sucking up the performance loss?
TCP interface for some older systems. In IIS5, I used to just spawn a
thread in Application_Start and clean it up when the app ended, and it
seemed to work fine. In IIS6 (winxp pro dev for a target of win2k3
production), it seems to be more aggressive about cleaning up apps and
generally have odd behavior when I spawn threads.
Am I doing something really wrong here? Should I be remoting everything
into a service and just sucking up the performance loss?