I am trying to write this in the most neutral voice I can.
We appreciate the advent of the new chat beta initiative. However, many of us are having unresolved issues with constant to sporadic ‘kicking’ or worse, room ‘kicking’ of members. Many of us lag now, high speed internet at home to t3 at work.
If it is possible, we are ok with giving up the new text editing features, the line count, etc, if you coulf roll back the previous chat room.
I’d rather chat in monochrome than not be able to effectively chat at all…
I have to agree. I really appreciate what you’ve done with the chat. We all do. However, when a room full of ppl all get dumped at the smae time, it’s hardly an enjoyable experience. Not to mention someone is always stalling after that happens. Of course with the advent of chat roulette, chat russian roulette would come about eventually. I would just pray that it not be our chat. ![]()
I have fou nd that I write one one page or box and it appears on another, sothere are problems.
as far as i can see, there are three issues that are slowing things down.
1.) heightgroup is served out of the root domain (i.e. NOT “www.heightgroup.com”), which means that cookies are sent with every request, even static images. Normally static content would be served out of a subdomain like “static.heightgroup.com”. This leads to massive overhead, esp w/ old cookies. I notice that the front page takes forever to load when i have an old session loaded, but if i delete the cookie, load the page, login, and load again, it loads instantly.
2.) the chat doesn’t seem to have much long polling/timeout ability, and i suggest the following: send the AJAX request and wait up to 30s if necessary. Internally the AJAX endpoint queries the data source every 5-10s. If the AJAX request times out (>35-40s), kill the thread, then wait 10s and send again. If the response header is ≠200, wait 1-2m, holding the room until then. If you couple this with queuing (both up- and down-stream), then the chat should at least appear more stable to the user.
3.) I’ve been told the chat runs from a database which makes for a great deal of overhead if the table is fully normalized. Even optimized views don’t relieve the processing necessary to manipulate the data in PHP. I’ve suggested a PHP socket server that interfaces with a PHP AJAX endpoint. It’s pretty lightweight, and there’s minimal overhead because both components are working with native, custom PHP data types. It also includes a queuing.
Many of the issues with the chatroom should have been fixed with the latest update today. I’d like to apologise that it took so long for me to get around to fixing the problems.
Any feedback on the now no-longer beta version of the chatroom is appreciated so that I can make sure it is working as it should be.
Admin.
Yeah, nice and stable. Private messages bump a little though – if you get the “cannot send message” box, the box you type in stays grey and won’t change.
A few further refinements have been put in place in the chatroom, including a block on double posts. Please continue to highlight any issues you may be having with the chatroom.
Admin.
Chat room seems to be more stable—but now it’s logging us in and immediately marking us as Idle.
It has been doing the idle thing for close to 12 hours, maybe more. annoying to say the least
Hi I keep getting marked as Idle and after each comment I say I get a box that I have to delete after each and every sentence I post to the room. Somethings I can deal with, but this one is wayyy annoying. Hope you know how to fix it…I wish I did.
Thanks
-downhere
It seems the issue – which was the result of an upgrade of the HeightGroup servers – has been corrected. Please let me know if any further issues persist.
You must be a member to post comments. Registering is free and only takes a few minutes!
To get the most from HeightGroup.com you'll need to log in.
Check out all of the latest posts in the Forums.