This product is different from anything you have seen before, it raises the bar for forums. It will make your forums much more interactive, and also reduce server load.
Technical Details:
If a thread has been posted in X seconds then its now Live, if other users are viewing the Live topic and are on the last page they will experience a clean ajax experience while talking to other members. Once the thread is older than X seconds its no longer Live and it will now act like a normal thread. Also if a user edits one of their posts that's inside of the thread, it will be updated too so there is no longer a reason to ever have to refresh.
There is also logic for the viewer, the viewer of the thread has to be in an active state to see responses. An active user state is determined upon the users actions, if no actions were made in X seconds then the user is marked as inactive.
Also you may wonder why this could save your server bandwidth and CPU. If a user is refreshing to talk to another members the queries on a normal thread load are way more intense than the ajax call that this modification makes. So if you have 5 people talking to each other none of them have to refresh the page, all they are doing is simple page requests and one intense request when there has actual change.
You can test Live Topic with two users, you will see how amaizing this is... And probably spontaneously combust.
This mod alters the 'post' table, which on a board with millions of posts can take quite a while, if the database doesn't run out of temp space while doing the alter.
Nope. I can put them together if I limit the vids to one forum, but then LiveTopic won't work in that forum. My users love the functionality of the vids, and I believe they would love this LiveTopic as well...
for information I don't get this error when the Ultimate Side Columns is disabled. But it still does not work.
Woot, read through the thread here to discover it doesn't work with USC... what a shame. Saved me a headache though trying to figure out what was causing it!
Also, I noticed it didn't work on my clean test board until I set Quick Reply to:
"Yes, Click Not Required"
I had to uninstall. My host says this puts too much server connections, and they would disable my account if i keep using it.
change the interval's
there is a query interval, right now its at 3000 by default. So every 3 seconds it makes a tiny query (which is alot a DB connection, but it should close right after)
there is also a setting that determines if the topic should be live or not right now if a topic has been posted in the past 300 seconds then its live (you can lower this number)
and third there is an idle setting that determines if the user viewing the page is idle right now that's set to 300 seconds. (when the user is marked as idle the query's will stop and they will continue when the system detects that the user is no longer idle)
so making any of these numbers higher will reduce server load, but the initial values seems fair to me. (shared hosting packages may need to have higher values)
Wow I really didn't mean to write an essay.
there is a st
Quote:
Originally Posted by Theater
Woot, read through the thread here to discover it doesn't work with USC... what a shame. Saved me a headache though trying to figure out what was causing it!
Also, I noticed it didn't work on my clean test board until I set Quick Reply to:
"Yes, Click Not Required"
This does look good, but are you sure about bandwidth? Yes it may save stress on the server but ive noticed Ajax being used like this uses mega bandwidth.
This does look good, but are you sure about bandwidth? Yes it may save stress on the server but ive noticed Ajax being used like this uses mega bandwidth.
how can it use more bandwidth?
the response is less than 1KB, the request is even smaller. Lets say every check call is about 250bytes (thats being generous) and a successful response with an updated post is 7KB.
20 calls a min (5kb).
a page refresh is like 70kb+
...
on an active topic you really think this wouldn't save bandwidth? (its CPU intensive, that's why you have the option to control the flow. If it really is hurting your server change it up.)
(this is just an example)
without livetopic:
example i go to a thread (70kb) (full page query + post generation)
i post a quick reply (10kb)
i wait 90 seconds and refresh this happens about 4 times (280kb) (full page query + post generation)
some one responds i respond to them (10kb)
i wait 90 seconds and refresh this happens about 2 times (140kb) (full page query + post generation)
total: 510kb
width livetopic"
example i go to a thread (70kb) (full page query + post generation)
i post a quick reply (10kb)
i wait 90 seconds (7.5kb) (tiny queries)
i recieve a response (7.5kb) (query + post generation)
i respond (10kb)
i wait 90 seconds (7.5kb)(tiny queries)
i recieve a response (7.5kb) (query + post generation)
the response is less than 1KB, the request is even smaller. Lets say every check call is about 250bytes (thats being generous) and a successful response with an updated post is 7KB.
20 calls a min (5kb).
a page refresh is like 70kb+
...
on an active topic you really think this wouldn't save bandwidth? (its CPU intensive, that's why you have the option to control the flow. If it really is hurting your server change it up.)
(this is just an example)
without livetopic:
example i go to a thread (70kb)
i post a quick reply (10kb)
i wait 90 seconds and refresh this happens about 4 times (280kb)
some one responds i respond to them (10kb)
i wait 90 seconds and refresh this happens about 2 times (140kb)
total: 510kb
width livetopic"
example i go to a thread (70kb)
i post a quick reply (10kb)
i wait 90 seconds (7.5kb)
i recieve a response (7.5kb)
i respond (10kb)
i wait 90 seconds (7.5kb)
i recieve a response (7.5kb)
total: 120kb
I say this because i had used a small ajax chat box which displayed all registered users who used it. Everytime somebody typed something their name will automatically appear. This was a small Ajax shoutbox and it had eaten a lot of bandwidth.
This is the same concept but slightly larger, it has to post avatar, icons, post table and message. Hence i think it will use much more bandwidth from what ive experienced before. Have you tried making large posts with a lot of text and large images? What happens then, how does the Ajax handle it?
Live Topic Details »»
About Developer
Visit Web Site
DB Changes 
Is in Beta Stage 
01-16-2009, 04:51 PM
