Quote:
Originally Posted by Coders Shack
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 live topic:
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 live topic"
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?