Quote from: alberthrocks on September 20, 2012, 10:31:45 pm

I'm surprised no one mentioned taking the time to redesign OmnomIRC and make it more efficient for servers and clients! That path would mean anybody could really host it, and there could be redundancy fallbacks when, say, Netham45's server goes down (and 4 other servers could take its place).

I've talked to Shmibs about how we possibly could redesign it, so that it is not dependent on a SQL database. Also, if there is a redesign, I think we should use WebSockets instead of the current implementation. I know it would mean no support for older browsers anymore, but it will be by far the easiest thing to do (and the best).

Also, about rehosting OmnomIRC: Don't forget that OmnomIRC was the cause of the outages on the current Omnimaga server, and I don't think the server has been changed meanwhile ?

What I think would be the best is to use the current longpolling method but use shared memory to save the database instead of SQL. PHP has the ability to create and use shared memory.

Netham, with websockets there wouldn't be a need for shared memory at all. Messages could instantly be distributed to other clients when they arrive. Of course this is fundamentally different and will not work on older clients.

That would mean i'd need to rewrite some of my bots
But i think go for websockets

Nope, it's just for the client/server of OmnomIRC. OmnomIRC will still be sending to IRC.
I'm highly doubtful that you would be able to access the websockets without being logged in somehow in your account, though...

I'd opt for shared memory for the sake of compatibility.

No, i mean the bots that do actual http requests and mess with omnomirc that way

Oh, like jimbauwen's New JS bot? Hmm, I guess...
Well, WebSockets != HTTP, but I see what you're saying. If a small chat server was run that would be like IRC, but for Omni only, you could alter your bots to connect to that, which would connect to IRC

Still, it's kinda uncertain as to whether we will support that protocol or not. Firefox 11, Chrome 16, Safari 6, and Opera 12.50 are the browsers that support it now, but older versions (such as browsers found in public areas) would not be able to use this. Furthermore, firewalls and filters may take action to block such a continuous stream.

I guess what could happen is WebSockets implemented in the backend, and have OmnomIRC simply be a frontend to it. Then OmnomIRC could relay said stuff into IRC, and keep a shortlog/log of convos. And bot devs might have an interesting API

Of course, this might be a lot more trouble than it's worth (and might be worse than OmnomIRC now!)... but it can't be that bad, right?

(For reference, Eeem's nodejs chat server uses only 1.1% of 1034452 KBs = 11.378 MBs of memory, which isn't bad, especially since nodejs is interpreted and whatnot. It might actually work! But I'll let the powers-that-is decide )

(For reference, Eeem's nodejs chat server uses only 1.1% of 1034452 KBs = 11.378 MBs of memory, which isn't bad, especially since nodejs is interpreted and whatnot. It might actually work! But I'll let the powers-that-is decide )

I would use a lot more if I started logging or supported multiple channels. Still though, it's snappy and doesn't use that much RAM.

I assume it would require a lot of work though? THat said, for the multi channel support issue, I guess you could just eliminate some channels that are rarely ever used, such as #omnimaga-radio, since juju's bot is almost never working, along with the extra 3rd-party channels such as #prizm, #nspire-lua and #irp.

I guess for the time being, colors wouldn't be that necessary except maybe Runer112's sprite converter bot (which Omnom itself doesn't support properly due to lack of white background support anyway), although moderator features might be a good idea to have eventually in case. Most people use Omnom to chat, anyway, not play Doom