blocks|key|1397185|text|我认为这里遗漏了一点:只对任何搜索引擎不需要知道的内容使用Ajax。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1397186|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think one point is missing here: Use Ajax only for content any search engine does not need to know.

blocks|key|1181490|text|98%25的用户将使用支持AJAX的浏览器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1181491|然而，很大一部分人在第一次访问你的网站时不会打开它(或者根本不会打开)。|1181492|我见过一些网站看起来就像一个没有打开javascript的空白页面。别成为他们中的一员。在我看来，用Javascript来修复布局问题是一个可怕的想法。确保它在没有Javascript的情况下加载和显示正常。如果人们至少能看到他们错过了什么，他们可能会打开它，但如果你的网站看起来像是坏了，那么……|1181493|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

98% of users will have AJAX enabled browsers.

A significant percentage of those people won't have it turned on when they first visit your site though (or at all, ever perhaps).

I've seen websites that look like a blank page without javascript on. Don't be one of them. Javascript to fix layout issues is a horrible idea in my opinion. Make sure it loads and looks ok without Javascript. If people can atleast see what they are missing out on, they are likely to switch it on, but if your website looks like it's just broken, then...

blocks|key|1396958|text|除非您的目标是移动设备或其他非标准web用户，否则您可以相当确定绝大多数都启用了Javascript，因为大多数主要站点(包括SO)都严重依赖它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1396959|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Unless you are targeting mobile devices or other non-standard web users, you can be fairly sure that the vast majority has Javascript enabled, because most major sites (including SO) rely heavily on it.

blocks|key|1181872|text|我的经验是，我们应该在ajax没有它的情况下使用它。有几个原因。首先，如果ajax中出现了问题，没有它就不能正常工作，那么站点就不能工作。例如，带有分页的产品列表。它应该只与链接一起工作，然后尽可能使用ajax。第二，用于站点索引和可访问性。如果没有ajax就可以工作，那就更好了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1181873|而且更容易打破一些东西(即使只是很短的一段时间)。一段糟糕的代码、未捕获的异常、未加载的外部库、阻塞的浏览器扩展……|1181874|在没有ajax的情况下一切正常之后，添加ajax就相当容易了。只需让ajax捕获操作，添加ajax=1，并在返回结果时，如果为ajax=1，则只返回所需的内容，否则返回所有内容。在产品列表示例中，我将只返回产品和分页html，并将其添加到正确的div。如果ajax停止工作，整个页面都会加载，客户会在加载时看到第二个页面。|1181875|Ajax为UX增加了很多价值。如果操作得当，用户在使用站点时会有很好的感觉，并且数据利用率更高，因为它不会每次都加载整个页面。|1181876|但问题是“什么时候不使用ajax"，我想说的是，你应该总是依靠它来改进用户体验，而不是依赖它来让站点工作(正如其他用户也提到的那样)。现在我们需要两者，优秀的代码和出色的用户体验。|1181877|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

My experience is, we should use ajax after it works without it. For a couple of reasons.
First, if something breaks in the ajax, and you don't have it working without it, the site simply doesn't work. For example, a product list with pagination. It should work with the links alone, then use ajax when possible.
Second, for site indexing and accessibility. If it works without ajax, it's better.

And it's easier to break something (even if only for a few moments). A bad piece of code, an uncaught exception, an external library not loaded, a blocking browser extension,...

After everything works without ajax, its quite easier to add ajax. Just have the ajax catch the action, add ajax=1 and when returning the result, return only what you need if ajax=1, otherwise return everything.
In the product list example, I would only return the products and pagination html, and add to the correct div. If ajax stops working, the whole page is loaded and the customer sees the second page as it loads.

Ajax adds a lot of value to UX. If done right, the user gets a great feel when using the site, and better data usage because it doesn't load the whole page everytime.

But the question being "when not to use ajax", I would say, you should always count on it to improve UX but not rely on it for the site to work (as other users also mentioned). And nowadays we need both, great code and great user experience.

blocks|key|1397021|text|我的做法是使用两个主页面，假设是index.py和ajax.py。第一个负责生成完整的网站，是表单的默认目标。另一个只生成特定于适当ajax查询的输出。它们背后的逻辑是相同的，只是生成输出的方法略有不同。在jquery中，我只是在发送请求时更改操作参数。它可以在ajax和没有ajax的情况下工作，尽管我很久没有看到有人禁用了js和ajax。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1397022|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My practice is to use two main pages, let's say index.py and ajax.py. First one is responsible for generating full website, and is default target of forms. Other one generates only output specific for adequate ajax query. Logic behind both of them is the same, only the method of generating output is a bit different.
In jquery I simply change action parameter when sending a request. It works both with and without ajax, although long time have I not seen someone with disabled js and ajax.

blocks|key|1397097|text|我喜欢这样的想法:在不使用JavaScript+/+Ajax的情况下编写应用程序，然后将其添加到应用程序中以增强UI，而不会因为用户没有启用JavaScript而剥夺他们的功能。我在专业的ASP.NET+MVC上读到了这一点，但我想我在其他地方读到过关于不引人注目的JavaScript的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1397098|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I like the thought of coding your application without JavaScript / Ajax and then adding it in later to enhance the UI without depriving users of functionality just because they don't have JavaScript enabled. I read about this in Pro ASP.NET MVC but I think I've seen it elsewhere in reading about unobtrusive JavaScript.

blocks|key|1397143|text|你不应该让你的服务变得臃肿，像手风琴，模态/+etc表单，图像缩放等Web2.0效果。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1397144|使用更智能的现代技术(AJAX就是其中之一)，你的用户会很高兴。不要害怕AJAX+--这是让用户体验流畅的一件非常好的事情。但不要因为你喜欢就去做--因为你的用户需要去做;)|1397145|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You should not make your service bloated with web 2.0 effects like accordion, modal/etc forms, image zoomers etc. 
Use modern tech smarter (AJAX is one of them) and your users will be happy. Do not fear AJAX -- this is very good thing to make user expirience smooth. But don't do things because you like it - do them because your user need it ;)

blocks|key|1181801|text|当你想让一个网站看起来像一个网站，而不是一个令人生厌的桌面应用程序时？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1181802|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

When you want to make a website that looks like a website, not a fugly imitation of a desktop app?

blocks|key|1181847|text|这完全取决于您正在开发的应用程序或功能的类型。如果应用程序在缺少Javascript的情况下仍可访问是至关重要的，那么使用备用方法(即替代形式)以允许用户使用上述功能/特性将会很有帮助。为此，您需要花费一些时间来开发收集信息的方法，不仅要使用客户端脚本，还要在服务器端收集信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1181848|对于仅用于增强用户体验的杂项功能，开发回退方法通常是不值得的。|1181849|没有理由完全不使用AJAX。毕竟，AJAX有助于最小化您的流量。|1181850|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This totally depends on the type of application or feature you're developing. If it is crucial that the application is accessible despite the absence of Javascript, then it would help to have fallback methods (i.e. alternative forms) to allow your user to use said functionality/feature. For that, it will require you to invest some of your time developing methods for collecting information not just using client-side scripts but also on the server-side.

For miscellaneous features that only serves to enhance user experience, it's mostly not worth it to develop fallback methods.

There's no reason to totally not use AJAX. AJAX helps minimize your traffic after all.

blocks|key|1181921|text|如果愿意，您可以始终使用AJAX并使用推送状态来更新历史状态，或者为了更好的兼容性，可以在不兼容HTML5的浏览器中使用散列。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1181922|这样，您就可以让服务器加载一个页面，然后javascript读取document.hash，并根据散列的状态恢复应用程序的状态。|offset|length|style|CODE|1181923|例如，我转到/index.html，我单击某些内容，例如，客户端打开视图客户端，您可以将散列更改为#/view/client/{client_id}/，然后如果使用浏览器重新加载或返回，散列将发生更改，您可以使用onhashchanged事件来捕获它，并将站点状态与新的散列进行匹配，如果收藏夹处于某个状态，则相同|1181924|entityMap^0|0|W|D|0|1D|Q|2Y|D|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|K|$]]

You can if you wish always use AJAX and update the history state using Push State or for more compatibility use the hash with none HTML5 compliant browsers.

with this you can have your server load a page then javascript read the <code>document.hash</code> and resume the state of the application base on the state of the hash.

for example i got to /index.html i click into something for example a client to open the view client you can change the hash to <code>#/view/client/{client_id}/</code> then if a reload or go back using the browser the hash with change and you can use the <code>onhashchanged</code> event to capture it and match the sites state to the new hash then same if a favorite a certain state

I'm building a web application with the Zend Framework. I have wanted to include some AJAX type forms and modal boxes, but I also want my application to be as accessible as possible. I want my application to be enhanced by AJAX, but also fully functional without AJAX.

So as a general guideline...when should I not use AJAX? I mean, should I bother making my application usable without AJAX? Or does everyone have AJAX enabled browsers these days?

When NOT to use AJAX in web application development?

我正在使用Zend框架构建一个web应用程序。我想包括一些AJAX类型的表单和模式框，但我也希望我的应用程序尽可能地可访问。我希望我的应用程序可以通过AJAX得到增强，但也可以在没有AJAX的情况下实现完整的功能。那么，作为一个普通的guideline...when，我应该不使用AJAX吗？我的意思是，我应该费心让我的应用程序在没有AJAX的情况下可用吗？还是现在每个人都有支持AJAX的浏览器？

问什么时候在web应用程序开发中不使用AJAX？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么时候在web应用程序开发中不使用AJAX？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么时候在web应用程序开发中不使用AJAX？
EN