< Back to James' Blog

No, I haven't been ignoring the fact that the chat room hasn't been working well,
rather trying to figure out a way to fix it... It was using a custom built server for a while, which made the requests about 10 times faster, but I was having trouble communicating data between the normal server and the custom server. For those wondering, the normal server is still being used because it's much more standards-compliant and feature-rich. The custom server was designed simply to handle the AJAX requests, and produced one of three codes when something happened: 200, 404, and 501. That's it... And that's really all it needed... But alas, I couldn't get the shared data to work properly.

I also was tyring to work on some security issues regarding the AJAX requests and setting cookies on a single domain. It was for that reason you were forced to log in again if you were viewing the site from matchstd.com and not www.matchstd.com. That problem is now resolved.

Remember, the chat is now VERY slow, and probably won't handle too many users, but I've set the site to restart on heavy load, so you shouldn't experience problems with anything else. Please have patience, I'll continue working on this one.

Remi and the CP team is about to release v3, which is just about as fast as the custom server. I'm porting the zippo structure to it, and hopefully that one will be behind the site. As it is we're getting build times of about .03 seconds per page, which is great, but of course, with the single server (shared) that we're on at the moment, it can be difficult to sustain the amount of requests the polling creates in the chat room. I'll also look into learning some more Java just to get something that works well, unless you guys would be interested in a simple Python+GTK system, which I could probably pull of in a week or two.

Take it easy, and keep up the feedback... Remember, WE CANNOT SEND YOU A RESPONSE TO FEEDBACK WITH THE FEEDBACK BUTTON IF YOU DON'T GIVE US CONTACT INFORMATION!

James

Comments