使用Web Garden模拟Web Farm会话问题？
我刚刚在 IIS 应用程序池中偶然发现了“网络花园”的概念。也就是说，当多个进程服务同一网页时。据我了解，这意味着 ASP.NET InProc 会话与网络场具有相同的问题。
我的问题是，假设您的生产环境是网络场，但您的开发/测试环境不是，那么在开发/测试中设置“网络花园”会有帮助吗？我认为这将有助于尽早发现任何多进程/服务器问题，或者至少确认一切都按预期工作。
I just stumbled across the concept of a "Web Garden" in an IIS App Pool. That is, when more than one process serves the same webpage. From what I understand, this means ASP.NET InProc sessions have the same problems as a web farm.
My question is, assuming your production environment is a web farm but your development/test environment is not, would it be helpful to set up a "Web Garden" in dev/test? I'm thinking this would help catch any multi-process/server issues early on, or at least confirm that everything works as expected.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我过去曾尝试过这个想法，它可能会有所帮助，但我想说它仍然不理想。为了获得最佳的测试场景，您只需使用与生产站点类似的硬件即可。
除此之外，网络园艺将帮助您处理一些项目和问题识别，具体取决于您需要如何使用它。
我们最大的问题是，我们有一些项目确实需要知道它们所在的服务器，而对于园艺，您在应用程序级别没有这种区别。
I have toyed with this idea in the past, it can be helpful, but I would say it still isn't ideal. To get the best test scenario you want to simply be on similar hardware to that of your production site.
Barring that though, Web Gardening will help you with SOME items and issue identification depending on how you need to work with it.
Our biggest issue with it is that we have some items that truly need to know what server they are on, and with gardening, you don't have that distinction at the application level.