I could write that and have before, but it was extremely difficult, very client-dependent and ultimately impossible to manage without a good CRON or scheduled task to handle chat persistence (somebody who just closes his/her browser w/o ever logging off formally). That's why I wanted something more manageable like an object that is not a browser to manage the chat session.
The classic chatroom scenario is to have an applet on the front end with an application on the back end to manage sessions/threads/stuff. You would be sitting on that box and able to manage it or have a CRON on the box to do it for you.
I want to recreate that exact same chatroom scenario, which has been a Java-based staple for years, except that instead of an applet I want an object of some other kind that when the user goes to the website to chat, a window pops up that is NOT THEIR BROWSER, but something like an applet, that would be where they can chat.
Phil