# AJAX Published articles for AJAX. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Single-Page Applications Can Become Performance Bottlenecks Through Multiple HTTP Round-Trips DevFeed: [Single-Page Applications Can Become Performance Bottlenecks Through Multiple HTTP Round-Trips]() Original publisher: [Read original article]() Author: Yegor Bugayenko (yegor256@gmail.com) Published: 2026-01-24T21:00:00Z Content type: opinion Language: en Sources: [Yegor Bugayenko]() Topics: [Single-page application (SPA)](), [web applications](), [HTTP](), [JavaScript](), [Web Development](), [Document Object Model (DOM)](), [Angular](), [React](), [Vue.js]() Tags: [ajax](), [applications](), [browsers](), [frontend](), [http](), [javascript](), [mood](), [performance](), [server-side-rendering](), [single-page-application](), [spa-performance](), [web-applications](), [web-architecture]() ### AI overview The article argues that Single Page Applications can become performance bottlenecks as they grow, because their frontends may require many HTTP round-trips to retrieve JSON and update the DOM. It contrasts this approach with full HTML page reloads and explains its historical origins in AJAX and web application frameworks. ### Source excerpt Single Page Applications, once a solution for slow browsers, are now a performance bottleneck due to multiple HTTP round-trips. ## Closing SSE Connections: A Browser Compatibility Deep Dive DevFeed: [Closing SSE Connections: A Browser Compatibility Deep Dive]() Original publisher: [Read original article]() Author: James Heller Published: 2025-11-20T19:00:00Z Content type: tutorial Language: en Sources: [Apartment 304]() Topics: [Server-sent events (SSE)](), [JavaScript](), [htmx](), [HTTP](), [Firefox](), [Chrome]() Tags: [ajax](), [apartment-304](), [browser](), [compatibility](), [custom-software-solutions](), [devops](), [devops-engineer](), [htmx](), [http](), [implementation](), [issue](), [javascript](), [multiplayer](), [software-architecture](), [software-development](), [software-engineer](), [sse]() ### AI overview This tutorial explains how Server-Sent Events connections can remain open inconsistently across browsers when users navigate away. Using the multiplayer mystery game Whodunit with HTMX as an example, it describes SSE connection tracking and a client-side JavaScript approach for robust cleanup. ### Source excerpt When browsers leave connections dangling, your app can get stuck waiting for users who are already gone. Let's solve the mystery of closing SSE connections. ## Ember without Ember Data DevFeed: [Ember without Ember Data]() Original publisher: [Read original article]() Published: 2013-03-23T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Ember](), [Persistence](), [API](), [jQuery](), [HTML]() Tags: [ajax](), [api](), [article](), [ember](), [javascript](), [persistence]() ### AI overview A tutorial explaining that Ember applications can use Ember's object model and AJAX-based data access without relying on Ember Data. It demonstrates modeling Reddit links, binding model properties to Handlebars templates, and accessing Reddit's JSONP API through jQuery. ### Source excerpt Update May 26, 2014 The concepts in this article are still true, but I've recorded a screencast showing how to use ember without ember data using ember-cli and the latest version of Ember. It goes beyond the contents of this article, showing how to create an adapter, store and even your own identity map. Check it out! Ember Data is a persistence layer for Ember.Js. Unlike Ember, which currently has a candidate for a 1.0 release, Ember Data is still very much a work in progress. This has been a source of confusion for people who are learning Ember, as the two frameworks are complimentary but currently exist in different realms of stability. ## Why Discourse uses Ember.js DevFeed: [Why Discourse uses Ember.js]() Original publisher: [Read original article]() Published: 2013-02-10T00:00:00Z Content type: opinion Language: en Sources: [Robin Ward]() Topics: [Ember](), [mvc](), [JavaScript](), [jQuery](), [Web Development]() Tags: [ajax](), [ember](), [interface](), [javascript](), [mvc]() ### AI overview The author explains why Discourse uses Ember.js, focusing on the benefits of client-side MVC for highly interactive web applications and the limitations of using jQuery as application state becomes more complex. ### Source excerpt This week, I was delighted to finally reveal Discourse, the app I've been working on for most of the last year in secrecy with awesome people. The launch got a lot of attention - we were featured on Hacker News, Slashdot, Wired, Reddit, Techcrunch and countless other places. Personally I've been floored with the amount of feedback so far. It's going to take quite some time to get through it all! One question people keep asking me is "Why did you choose Ember.js?". It's a good one, and one that I think can be considered in two ways: "Why use a a client side MVC Framework?" and "Why Ember out of all the frameworks?" Here's my answer to both of those questions. ## Turbolinks animated page transitions DevFeed: [Turbolinks animated page transitions]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2013-01-22T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [animations](), [Ajax](), [nginx]() Tags: [ajax](), [animations](), [nginx]() ### AI overview The article explains how the author added animated page transitions to a Turbolinks-based application. It describes using a gem and importing JavaScript, with an animated GIF illustrating the result. ### Source excerpt Since I've seen the new Basecamp, I fell in love with it. ## Turbolinks and the Prague Café Effect DevFeed: [Turbolinks and the Prague Café Effect]() Original publisher: [Read original article]() Published: 2013-01-06T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [web applications](), [Rails](), [Ruby](), [JavaScript](), [Ajax](), [Web Development]() Tags: [ajax](), [cdn](), [javascript](), [rails](), [ruby](), [speed](), [web-applications]() ### AI overview The article explains how Turbolinks, a Ruby library enabled by default in Rails 4, uses background AJAX requests and replaces page content without repeatedly downloading static assets. It argues that geographically distributed Content Delivery Networks can improve web application performance for users far from a site's servers. ### Source excerpt Turbolinks Turbolinks is a new Ruby library, enabled in Rails 4 by default, that is designed to speed up your web applications. It does this by binding a Javascript handler to all link clicks. Instead of allowing the browser to load the new page, it fetches it in the background via AJAX. It then parses out the body, and injects it into the document you're currently viewing. The main advantage of Turbolinks is that your static assets such as Javascript or CSS will not be downloaded or parsed every time a link is clicked. This can result in a significant client side speed improvement for your end users. ## Rails AJAXSpin DevFeed: [Rails AJAXSpin]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2012-11-26T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Rails](), [Ajax](), [opensource]() Tags: [ajax](), [opensource](), [rails]() ### AI overview The author describes gemifying an AJAX status spinner originally built with CoffeeScript for Ruby on Rails and invites readers to install, fork, comment on, suggest improvements to, or contribute to it. ### Source excerpt A couple of days ago I wrote about how to build a simple and non intrusive AJAX status with CoffeeScript in RubyOnRails. ## Building a Non-Intrusive AJAX Status Indicator with CoffeeScript DevFeed: [Building a Non-Intrusive AJAX Status Indicator with CoffeeScript]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2012-11-08T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Ajax](), [Library]() Tags: [ajax](), [loading](), [tutorial]() ### AI overview A tutorial on building a CoffeeScript AJAX status indicator with spin.js that shows and hides a loading spinner without blocking application interaction. It discusses handling AJAX lifecycle events and avoiding premature hiding when multiple requests occur. ### Source excerpt tl;dr ## HTML5 Taking over the app world - Touchlab DevFeed: [HTML5 Taking over the app world - Touchlab]() Original publisher: [Read original article]() Published: 2012-07-03T19:59:00Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [HTML5](), [Mobile](), [App](), [WebView](), [cross-platform](), [JavaScript](), [Ajax]() Tags: [ajax](), [code-sharing](), [cross-platform](), [development](), [html5](), [javascript](), [mobile](), [thoughts](), [webview]() ### AI overview This opinion argues that HTML5 could serve as a mobile app platform, but Apple and Google have little incentive to support it within their app ecosystems. It discusses WebView limitations, the author's experience with JavaScript and Ajax, and broader cross-platform development examples. ### Source excerpt I think you might read that title and think this is going to be about how HTML5 is steadily taking over the native app world on mobile devices... ## Review of Using Google App Engine by Charles Severance DevFeed: [Review of Using Google App Engine by Charles Severance]() Original publisher: [Read original article]() Author: Guido van Rossum (noreply@blogger.com) Published: 2009-06-15T16:20:00Z Content type: opinion Language: en Sources: [Guido van Rossum]() Topics: [Web Development](), [Programming](), [Python](), [JavaScript](), [CSS](), [HTML](), [Caching](), [Ajax]() Tags: [ajax](), [appengine](), [book](), [book-review](), [caching](), [css](), [google](), [html](), [javascript](), [python](), [web]() ### AI overview A review of Charles Severance's book Using Google App Engine, describing it as an introductory resource for web programming and App Engine. The book covers enough HTML, CSS, Python, and JavaScript to help beginners create dynamic websites, including datastore models, forms, simple AJAX patterns, caching, and debugging, while directing readers to other resources for deeper study. ### Source excerpt At Google I/O I received a copy of Using Google App Engine by Charles Severance, published by O'Reilly. I haven't kept track, but this appears one of the first App Engine books to actually hit the stores -- an Amazon search for App Engine showed up one other book (Developing with Google App Engine by Eugene Ciara, published by APress) and many titles available for pre-order (including additional titles from the same publishers). Severance's book is a quick read if you're already familiar with the basic premises of web programming. I think it would do well in an introductory course about the topic. (The author teaches at the University of Michigan so this is likely how he developed the material in the first place.) In fact, quite a bit of the book could well have come from a pre-existing earlier course: the chapters on HTML, CSS, Python and JavaScript barely mention App Engine. Don't get me wrong, I think that's a good approach: in my experience quite a few App Engine users are new to web programming in general, or could at least use a refresher course. If you don't fall in this category, don't feel offended: you just probably aren't the intended audience for this book. On the other hand, if you've developed for the web but haven't used Python before, you could probably just skip the HTML/CSS chapter and dive right into Python and App Engine. If you're a blank sheet where it comes to programming, don't expect to come out an experienced Python developer: the book only covers enough of the language so you can get started with App Engine without feeling you're just copying and pasting text. The same is actually true for any topic covered -- in many cases the book actually recommends that you study a topic more in-depth using other resources. But in each case the book's coverage is enough to get you started with the creation of dynamic web sites, and that's the important part. After all, you didn't learn your mother tongue by studying the rules of grammar either: you lea ## AJAX, IE6 and System error: -1072896658 DevFeed: [AJAX, IE6 and System error: -1072896658]() Original publisher: [Read original article]() Author: Graham King Published: 2008-02-08T02:43:05Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Ajax](), [Microsoft](), [Query (disambiguation)](), [Server](), [Firefox]() Tags: [ajax](), [firefox](), [html](), [microsoft](), [query](), [server](), [software](), [text]() ### AI overview A troubleshooting note about an IE6 AJAX error when reading responseText through Microsoft.XMLHTTP. The reported fix is to return the correct MIME type, such as text/plain for plain-text responses. ### Source excerpt I have just spent a while wrestling with this problem, so in case anyone else comes across it. Symptoms - You are making an AJAX query to your server - in my case using Yahoo's excellent YUI, connection manager. - On IE6, using the Microsoft.XMLHTTP object, you try and read the responseText parameter (or the YUI does for you). ## Technologies for better web based applications: XMPP, Flex, and more DevFeed: [Technologies for better web based applications: XMPP, Flex, and more]() Original publisher: [Read original article]() Author: Graham King Published: 2008-01-27T20:39:52Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [web applications](), [Ajax](), [XMPP](), [real-time](), [Single-page application (SPA)](), [JavaScript](), [Firefox extension]() Tags: [ajax](), [applications](), [extension](), [firefox](), [futureofwebapps](), [http](), [javascript](), [software](), [summary](), [web](), [xmpp]() ### AI overview The article explains how web applications differ from traditional websites, focusing on richer graphical interfaces and real-time data. It discusses JavaScript, Adobe Flex, Firefox extensions, AJAX, Comet, and XMPP as approaches for building more interactive and connected applications. ### Source excerpt The web application revolution: blurring the line between websites and software. ## Tom Coates - Native to a Web of Data DevFeed: [Tom Coates - Native to a Web of Data]() Original publisher: [Read original article]() Author: Graham King Published: 2006-03-11T18:45:43Z Content type: article Language: en Sources: [Graham King]() Topics: [Web](), [data](), [API](), [interface](), [XML](), [RSS](), [Web platform](), [Ajax]() Tags: [ajax](), [api](), [data](), [futureofwebapps](), [html](), [interfaces](), [network](), [platform](), [rss](), [society](), [software](), [web]() ### AI overview This article summarizes notes from Tom Coates' Future Of Web Apps presentation about moving from linked web pages toward a web of data connected by APIs. It discusses designing around addressable, reusable data objects; providing HTML, API, and XML interfaces; using RSS for list pages; and preserving stable, predictable URLs while supporting manipulation interfaces. ### Source excerpt Navigating the future: Web 2.0 insights from Tom Coates. ## Cal Henderson - Building Flickr DevFeed: [Cal Henderson - Building Flickr]() Original publisher: [Read original article]() Author: Graham King Published: 2006-02-18T13:39:52Z Content type: article Language: en Sources: [Graham King]() Topics: [Web](), [web applications](), [API](), [Ajax](), [Mod\_rewrite](), [XML](), [Mobile](), [Open Data](), [export](), [import](), [Firefox]() Tags: [ajax](), [api](), [export](), [firefox](), [futureofwebapps](), [import](), [mobile](), [mod-rewrite](), [notifications](), [software](), [web]() ### AI overview Notes from Cal Henderson's talk on building Flickr, covering collaboration, data aggregation, public APIs, clean URLs, AJAX, Unicode, desktop and mobile integration, open data, and open content. ### Source excerpt Build Flickr: Lessons from the Web 2.0 Pioneer.