Hello,
I've been a long term user of this great module but I've been having alot of issues with how server-heavy the reloading script is, and I have a request on which I need help fast.
First of all, I'd like to know which part of the code should I change/remove, so the user will not be let to reload (via the Reload button) the chat manually but will have to wait for the auto-reload. This is, so there won't be cases of anyone who might hit Reload repeatedly which would hammer the server CPU badly, and since Reloading manually is not controlled.
Another request, apart from the obvious request of finding a way to use less-heavy reloading is to maybe put a limit of reloads per 10 seconds for example, and don't let Tribune reload until spots free, which I think will help drastically on the heaviness by managing the reloads.
But only an answer of the first question will be more than enough, since I think that will help alot too.
Thanks!
Comments
Comment #1
SeeSchloss commentedSorry for answering this late, but in case anyone needs an answer...
The easiest way to do that would be to replace "return true" with "return false" on line 281 of js/tribune.ajax.js (line 302 for 6.x-1.x). This would prevent reloading when clicking the "reload/post" button or hitting enter when the textfield is empty.
Regarding the other request, yes that's a good idea, probably not too easy to implement but I will think about it... for 7.x-3.x
Comment #2
SeeSchloss commentedWith the Nodejs and Pyroly.se modules, this shouldn't be a problem anymore.