Hashify.me - store entire website content in the URL

Re:Hashify.me - store entire website content in the URL by hashify on Tuesday April 19, 2011 @06:36PM (#2464512)

> they'd just send down a small bit of constant Javascript that rebuilds the page from the #fragment.

That's _exactly_ what the site does. Everything happens client-side. nginx serves a single index.html for every request. ;)

[ Parent | on HN ]

Re:Hashify.me - store entire website content in the URL by gbhn on Tuesday April 19, 2011 @07:13PM (#2464617)

The OP is saying that with a #fragment, the browser wouldn't even need to send the server the doc contents. (Since they aren't used anyway, there's obviously no use in doing so.)

[ Parent | on HN ]

Re:Hashify.me - store entire website content in the URL by gojomo on Tuesday April 19, 2011 @07:10PM (#2464606)

Then why put the encoded content in the /path-info rather than the #fragment?

[ Parent | on HN ]

Re:Hashify.me - store entire website content in the URL by AndyKelley on Tuesday April 19, 2011 @07:13PM (#2464616)

It looks nicer.

[ Parent | on HN ]

Re:Hashify.me - store entire website content in the URL by metamatt on Tuesday April 19, 2011 @11:04PM (#2465090)

And gratuitous roundtrips are fun, too :P

(You're uploading the data in order to then convert it client-side. Groxx noticed this too: http://news.ycombinator.com/item?id=2464347)

[ Parent | on HN ]