Let’s chat!
Just in time for CodeRage II, we are launching a public beta of our new chat server. We have a draft of the user guide available on the Developer Network. We’ll be using the new chat server for live Q&A during CodeRage sessions.
Come join us for CodeRage II, and feel free to help test out the new chat server interface right now, and give us feedback! You can see the current open chat room status at http://chat.codegear.com, and just click to join a chat.
Share This | Email this page to a friend
Posted by John Kaster on November 20th, 2007 under CDN |10 Responses to “Let’s chat!”
Leave a Comment
Server Response from: dnrh1.codegear.com
RSS Feed
November 20th, 2007 at 11:30 pm
Looking forward to Coderage II
November 21st, 2007 at 12:02 am
This is great - and I can see that some words, like CodeGear and CodeRage become links, nice done
I would love to see some integration with other jabber compatible services, like Google Talk…
November 21st, 2007 at 5:03 am
Is there a page somewhere that describes the technical requirements for getting the sessions to work well? How much bandwidth do we need? What browser works best? Any specific firewall or security settings we need to tweak? Is there a "test session" running somewhere so we can get things "tuned up" in advance, so we’re not fussing with it for the first two hours instead of hearing and seeing the sessions?
November 21st, 2007 at 5:08 am
I did find some of this stuff on the site, but not the bandwidth question.
November 21st, 2007 at 5:59 am
When I try to register for code rage I get the following:
Internal Application Error
Trying to store a string of length 30 into a field that can only contain 20
/default
30 doesn’t seem like a lot for an email address
November 21st, 2007 at 11:49 am
Lars: I’d like to get our own Jabber interface available first. There are plug-ins for OpenFire for other IM systems, so GoogleTalk and others are certainly feasible. Depends on how our server scales, I suppose!
Steven: for our JWChat browser interface, only port 80 is required. XMPP is a bit chatty however, so it’s not going to be as efficient as a binary protocol. I don’t know about bandwidth needs yet, sorry. Some analysis will be doing will help.
Gene: I’ll let Christine know the email field is too short. In our main customer database, I think it’s 80 chars, or whatever the RFC limit indicates. This CodeRage registration implementation should only be used for this one CodeRage. The next one should be using our existing customer account system.
November 21st, 2007 at 12:21 pm
Gene: Spoke with Anders about the field length issue, and it’s not the email address since that can’t even be changed .. it’s probably the password field. Hope that helps.
November 21st, 2007 at 12:44 pm
I had a chance to try it out a little with FireFox 3 beta 1 (MineField :), and I didn’t have any problems.
Looks really good. Looking forward to CodeRage.
November 23rd, 2007 at 10:13 am
Thanks for the compatibility report, Bruce
December 5th, 2007 at 10:39 am
Thanks for CodeRage, was great!