1–1011–2021–24

XSLT/XML vs. JSON

From: Ally 4 Nov 2010 21:17
To: af (CAER) 20 of 24
37750.20 In reply to 37750.19
There are some JS plugins (I've used ReallySimpleHistory before) that handle history state and such.

It's still a pain, though.
EDITED: 4 Nov 2010 23:53 by ALLY
Reply
0/0
From: Matt 4 Nov 2010 21:33
To: af (CAER) 21 of 24
37750.21 In reply to 37750.19
jQuery hashchange is better, seeing as you're already using JQuery.

(For your forum thing that is.)
EDITED: 4 Nov 2010 21:37 by MATT
Reply
0/0
From: af (CAER) 4 Nov 2010 21:37
To: Matt 22 of 24
37750.22 In reply to 37750.21
Oo cheers, I'll keep that in mind!
Reply
0/0
From: Ally 4 Nov 2010 23:58
To: af (CAER) 23 of 24
37750.23 In reply to 37750.19

It is one of the reasons I've been looking at XSLT/XML pages. The XSLT files are totally cachable, so when you're looking at similar pages of content (i.e., forum posts) you can use the template over and over again.

 

Low bandwidth! Huzzah!

Reply
0/0
From: THERE IS NO GOD BUT (RENDLE) 6 Nov 2010 09:44
To: Ally 24 of 24
37750.24 In reply to 37750.23
Javascript's cacheable too, and if you use one of the free public CDNs for jQuery, chances are it's already cached on the client's device anyway. Microsoft's CDN even includes the templating/binding extension, which sounds ideal for what you're doing.
Reply
0/0