ASP.NET 禁用页面级缓存问题/危险?

发布于 2024-10-20 18:08:00 字数 473 浏览 2 评论 0原文

基本上,我禁用缓存的原因是因为我有 DevExpress ASPxGridViews,它非常适合过滤、排序等,但客户端正在处理大量数据,并要求我们在页面导航之间保存过滤/排序。

完成此操作的方式是通过发生的事件 ClientLayout。问题是,当用户导航到不同的页面,然后单击浏览器的“后退”按钮时,事件不会触发,并且会显示未过滤的网格,大概是因为这是缓存的内容。 (但是,返回网格页面的链接会导致页面正确加载,并触发事件。)

我能够解决该问题的唯一方法是禁用缓存,如此链接中指出的: http://forums.asp.net/p/1304752/2563283.aspx

显然,仅仅因为我能做到,并不意味着这是一个好主意。我知道这可能会影响性能一点,但谁能告诉我可能发生的任何其他问题? 也许是 AJAX 问题或控件出现意外行为?

Basically, the reason I am disabling the cache is because I have DevExpress ASPxGridViews, which work great for filtering, sorting, etc. but the client is working with large amounts of data and has requested that we save the filter/sort between page navigations.

The way this is done is via an event that occurs, ClientLayout. The problem is, when the user navigates to a different page, and then clicks the browsers Back button, the events do not fire, and the unfiltered grid is displayed, presumably because this is what was cached. (However a link back to the grid's page causes the page to load properly, and the events to fire.)

The only way I have been able to solve the problem is to disable caching as pointed out in this link:
http://forums.asp.net/p/1304752/2563283.aspx

Obviously, just because I CAN do it, doesn't mean its a good idea. I understand it might affect performance a bit, but can anyone tell me of any other problems that might occur?
Maybe AJAX problems or controls giving out unexpected behaviour?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

生生漫 2024-10-27 18:08:00

除了性能降低之外,我们不知道任何可能的问题。

We are unaware of any possible problems except for performance reduce.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文