现代仅限 Intranet 的 Web 应用程序是否仍应使用框架？
我想询问有关在现代仅限 Intranet 的 Web 应用程序中使用框架的问题。 当然，在现代互联网 Web 应用程序中使用或不使用框架有几个原因。 但是当涉及到 Intranet Web 应用程序时（想想金融应用程序）呢？
考虑一下应用程序中大多数时间持续可见的部分（如工具栏、菜单、标识等），其中框架可以成为简单/更快的解决方案？ 如今，在考虑 PPR 等产品时，这些优势是否重要？
我很好奇，也很感谢你对此的看法。
I'd like to ask about using frames in a modern intranet-only web application.
Of course there a several reasons to use or probably not use frames in a modern internet web application.
But what about when it comes to an intranet web applications (think about a financial application)?
Think about parts of the application which are most of the time constantly visible (like a toolbar, menu, identity et cetera), where frames can be a simple/faster solution to do things?
Are these advantages that count these days when considering things like PPR?
I am curious and both thankful about your view on this.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
框架并不是天生邪恶的，但它们确实带来了其他方法不会面临的挑战。既然您谈论的是 Intranet，您可能并不关心：
总体而言，可能没有一个突出的理由躲开他们。不过，我认为您没有提供令人信服的理由使用它们。
然而：我发现您在使用丰富互联网应用程序时遇到的一个问题是不同页面/组件之间可能需要相互通信。框架对于脚本编写来说可能是一个令人头疼的问题，仅出于这个原因，我就避免使用它们。
Frames aren't inheritly evil, but they do create challenges that other approaches don't face. Since you're talking about intranet you probably aren't concerned about:
Overall there probably isn't an outstanding reason to dodge them. However I don't think you've offered a compelling reason to use them.
However: the one issue I could see you running into with a rich internet application is the potential need for your differing pages/components to talk with one another. Frames can be a royal headache with scripting, and for that reason alone I avoid them.
CSS、ASP.NET 母版页和大量其他技术使得框架变得不必要，更不用说难看了。
并不是说你不能使用框架，只是你应该避免使用框架，因为它们看起来有些不专业。对我来说，帧与 GIF 动画处于同一水平。
CSS, ASP.NET master pages, and tons of other technologies make frames unnecessary not to mention unsightly.
It's not that you can't use frames, it's just that you should avoid frames as they look somewhat unprofessional. To me, frames are on the same level as animated gifs.
我认为没有令人信服的理由在现代 Web 应用程序中使用框架。现代标记技术即使不是更容易维护，也解决了框架的一些问题（您永远无法为任何内容添加书签，很难设置页面标题等）。框架的大多数缺点都可以解决，但为什么要麻烦呢？
I would argue that there's no compelling reason to use frames in a modern web application. Contemporary markup techniques are just as, if not more easily maintainable, and solve some of the frustrations of frames (you can never bookmark anything, it's difficult to set the page title, etc). Most of the drawbacks of frames could be worked around, but why bother?
正如其他人所说，框架几乎已经成为过去。一个主要的例外是在处理文件时，如果您想要类似 ajax 的体验并让用户上传文件，iframe 是唯一的方法（目前）。
As everyone else said, frames are pretty much a thing of the past. One major exception is when dealing with files, if you want an ajax like experience and are having the user upload files, iframe is the only way to go (for now).
无论如何，框架都令人沮丧。使用 AJAX 来刷新页面中正在更改的部分怎么样？假设您没有被困在使用 IE6 中。
Frames are frustrating no matter what. What about using AJAX to just refresh the parts of the page you are changing? Assuming you aren't stuck using IE6.
框架绝对不应该用于工具栏或菜单。当 DOM 在页面之间完全匹配时，浏览器会缓存 DOM，这使得 iframe 充其量是无用的，而充其量是有害的（双重包含 JS 库等）。
也就是说，框架有一些特定的用例，这使得它们变得必要。然而，在您遇到它们之前，您并不需要它们。
Frames should definitely not be used for toolbars or menus. Browsers cache the DOM when it matches exactly between pages, making iframes useless at best, and harmful at worst (double inclusion of JS libraries and such).
That said, there are specific use-cases for frames that make them necessary. Until you run into them, however, you don't need them.
主啊，不。无论是否是内部的，你为什么要使用框架，它们又旧又过时，而且需要死得很惨。
相反，如果您觉得无法打破范例，请使用
代替。不要误会我的意思，如果您确实决定使用框架，宇宙不会崩溃，但标准不再真正支持它们，您可能会将 IE 踢入 Quirks 模式并最终结束更让人头疼。更不用说您最终会让您的用户与上下文发生冲突，并且该网站根本不会对智能手机友好。
Lord no. Internal or not, why would you use frames, they're old and antiquated, and need do die a horrible death.
Instead if you feel you CANT break the paradigm, use an
<iframe>instead.Don't get me wrong, the universe won't crumble if you do decide to use frames, but they're not really supported by the standards anymore, you might kick IE into Quirks mode and end up with more of a headache. Not to mention you will end up having your users fight with contexts and the site wont be smart-phone friendly at all.
基于框架和表格的布局肯定会被 CSS 克服。 （--> 否）
A layout based on frames and tables is definitely overcome by CSS. (--> no)