a "simple" and unified approch to implement the new HTML5 History Interface & loading content via ajax
JavaScript CSS
Latest commit 9867816 Jan 30, 2014 @lautr Update version.txt
Failed to load latest commit information.
demo Update asfar.min.jquery.js Dec 11, 2013
source remove a nasty bug that would strip get parameters after page load fr… Aug 22, 2013
GPL-LICENSE.txt updating asfar and adding license Nov 25, 2011
README.md Update README.md Dec 11, 2013
asfar.min.jquery.js new minified version Aug 22, 2013


asfar - ajax substitute for (all) requests

asfar is a "simple" approch to implement the new HTML5 History Interface or shebangs (depending on Browser Capability) to load content via AJAX to a specific DOM Target and keep track of that in the History & Adress Bar of the Browser.

In its current Form asfar is an jQuery Plugin and need the Library to function, depending on the feedback this might change in the future.


The main goal of asfar is to provide an easy way (just look at the basic implementation) to Access and Reffer Information/States of Content that is provided via AJAX and work with them, most likely show them in some way on the page, whyle keeping track of thoose changes in the History & Adress Bar of the Browser.

If your Browser does not support the HMLT5 History Interface (yes IE Users, I'm looking at you), the functionality is the same only that shebangs are used (like Facebbok does in general for Example).


Plain: http://lautr.com/sandbox/asfar/example-plain/start.html

Effetcs using Callbacks: http://lautr.com/sandbox/asfar/example-fancy/start.html

implementation & Examples




         selector : 'a:not(.extern)'


        selector : 'a:not(.extern)',
        before : function(urlFragment,target){
        insert : function(urlFragment,target,data){
        after : function(urlFragment,target){
        success : function(urlFragment,target){
            if(0 > $('a[href="' + urlFragment + '"]').length){
                $('a[href="' + urlFragment + '"]').addClass('active');


Server Side

You can optimize your application to only return the part of the page that you actually want to load, you can do that by recognizing an "ajax" call and delivering different/partial content depending on that.

Client Side

You can place this peace of javascript Code in the header of your page so he can perform redirects without loading & showing the whole (wrong) page first

        if ('#!' === location.hash.substring(0,2)) {
            location.href = location.hash.substring(2);