HTML5 History API Support about director HOT 8 CLOSED

I wrote about this in the readme.md. the pushState API is a load of shit IMO, pun intended. But, since some people think its good (usually because they dont understand what the implications of its use are, and because backbone is popular) i guess its worth supporting. I dont feel highly motivated to implement it.

from director.

What don't you like about the History API? It rocks if you use it right. Another strategy is this: have your server map any not found routes to the app's main route and let the client do its thing from there, so if a deep link is bookmarked you're still covered. In that case the main benefit is prettier URLS: /articles/html5 instead of #/articles/html5, you still have no SEO. But now you've got the option to fill in the blanks on the server with indexable content, here and there, where it makes sense for SEO. Beats using Google's hashbang (/#!/) mess if you ask me.

from director.

I wrote a blog post here (http://blog.nodejitsu.com/single-page-apps-with-nodejs), and i explain some of the reasons why i think that the History API does not rock. Web 1.0 style applications, and APIs that promote them don't get me excited.

Edit: I think /#!/ and pushState API are both poor solutions. Apps dont need SEO, i agree websites do. Does anyone ever deep link to a garage-band dialog or a photoshop menu? Client side routing is for building rich UIs.

Edit: that said, if someone had a pull request for this feature and it looked good, i'd probably accept it =)

from director.

Good article with valid points. OSX Lion kinda deep links apps with its new Resume feature, and opening a file with a program is a similar concept. But anyway, you're probably right. If SEO is your #1 thing you should build a site, with as much app-like goodness as you can progressively add in. I've just been thinking lately that it may be feasible to build a web app (single page app) and later add a server-side runner for the spiders. In the past this would have been way too much work, creating a client side and a server side version of your app. But now that there's Node with jsdom that can run your web app on the server...maybe it's an option? It would be nice to not have to choose between SEO and UX.

from director.

yea, definitely want this feature.

from director.

I just wrote about this topic a bit, with a code sample of how an isomorphic framework could work with routing History API updates and server side deep URL requests. More Thoughts On Frameworks @ solberg.is.

from director.

you're saying you want to make a pull request? go for it ;)

from director.

Pull request is open, duplicated issue

from director.