|
Post by Marlon on Sept 8, 2005 17:26:46 GMT -5
Jim,
How about a webbrowser based java c64 emulation client for your project that connects to your server? You'd have the benefit of portability and the convenience of loading up Q in your browser.
I would gladly help out with this, as I do have java expertise.
The other idea was to harness the AIM servers to handle most of the 'live' traffic like chatrooms, OLMS and games. The benefit would be greater scalability.
We could implement a translation layer for aim events into Q-Link tokens. This would mean we'd have to pass custom sub-tokens over aim's protocol - would take a bit of creativity.
If we went the java applet path, area content like message boards could be fetched from webservers on the client side, rather than through your server. This would take a huge load off.
Of course there's issues with going through the AIM server, like account management, 16 letter screennames, max limit 36 instead of 23 for rooms, etc.
|
|
|
Post by Jim Brain on Sept 8, 2005 22:26:14 GMT -5
I'd love a Java applet. That was in the plans, but I'm no applet writer.
Integration is tough, because of the limits in PC rooms (23 users, et al). I also worry about AIM integration, as that means people need AIM passwords, etc. I have been looking at the IRC protocol, as no passwords are needed, it supports OLMs and real time chat, etc.
The client web pulls are fine, but if they want the same content, they'd need to access the server for the data at least, via Apache.
Initially, I'd be happy with a java applet that simly offers access to the service. As I mature the service, the goal is to farm data out to web sites instead of housing locally.
Jim
|
|