clamcrusher
09-21-2004, 09:53 PM
Is this something in the works yet?
For a long time ive wanted to make a "module" for vbulletin which would allow users to see the next page in a thread, without having to reload the whole page. Significant bandwidth savings and resultingly less congested network, and i would imagine greatly decreased perception of page load time for users.
for example, lets say the forum defaults to showing 20 posts per page. each post could be given an id such as "post1" and then "post2" etc....
if the user clicked on the "next" link which would show them the next 20 posts in the thread, the entire page would not be reloaded. Instead, javascript would send a http request to the server, specifying which posts to give it, all in the background and transparently to the user. The server would need to output the queried posts as text/xml. Each post would be given an id attribute which would correspond to 1-20 "placeholders" in the already downloaded page.
Then, javascript simply swaps the content of id="post1" through id="post20" dynamically, replacing it with the new content fed from the server, and then of course load any new images in the posts yada yada.....
i had been (slowly) working on this for a while and must admit im very unfamiliar w/ javascript, but php im fluent. I just found out about the
XMLHttpRequest object and how it is widely supported by browsers, and how trivial it makes a task like this.
heres a demo of the concept
http://developer.apple.com/internet/webcontent/XMLHttpRequestExample/example.html
so again, is this currently being developed, or is it just a lot of work for little benefit? I really have no idea how much savings this would provide above and beyond Gzip, maybe its very little. But still.....
For a long time ive wanted to make a "module" for vbulletin which would allow users to see the next page in a thread, without having to reload the whole page. Significant bandwidth savings and resultingly less congested network, and i would imagine greatly decreased perception of page load time for users.
for example, lets say the forum defaults to showing 20 posts per page. each post could be given an id such as "post1" and then "post2" etc....
if the user clicked on the "next" link which would show them the next 20 posts in the thread, the entire page would not be reloaded. Instead, javascript would send a http request to the server, specifying which posts to give it, all in the background and transparently to the user. The server would need to output the queried posts as text/xml. Each post would be given an id attribute which would correspond to 1-20 "placeholders" in the already downloaded page.
Then, javascript simply swaps the content of id="post1" through id="post20" dynamically, replacing it with the new content fed from the server, and then of course load any new images in the posts yada yada.....
i had been (slowly) working on this for a while and must admit im very unfamiliar w/ javascript, but php im fluent. I just found out about the
XMLHttpRequest object and how it is widely supported by browsers, and how trivial it makes a task like this.
heres a demo of the concept
http://developer.apple.com/internet/webcontent/XMLHttpRequestExample/example.html
so again, is this currently being developed, or is it just a lot of work for little benefit? I really have no idea how much savings this would provide above and beyond Gzip, maybe its very little. But still.....