search

zenirc / zenircbot

An IRC bot that knows nothing of its past, nor its future.
http://zenircbot.rtfd.org/
MIT License
56 stars 19 forks source link

discuss the merits of having the bot be polyserver as well as the implications therein #43

Open wraithan opened 12 years ago

wraithan commented 12 years ago

SEPoCoNi will be a good start. I'll toss notes in here.

wraithan commented 12 years ago

Polyserver looks pretty easy on the surface, but the problem comes when you have anything channel specific in your services. You then have to check both the server and the channel, as well as always sending back the server when you reply to something. External services also need to know what you call the server.

On the other hand it lets you run a single bot against multiple servers using one set of services and a single redis db. This may not outweigh the complexity overhead.

hackervera commented 12 years ago

I vote one bot per server, but have a system for controlling bot processes

wraithan commented 12 years ago

Well, for each bot process, I'd be instantiating it once per server and keeping it in a list. So they'd be separate sub processes, and manageable in that way.

wraithan commented 12 years ago

Closing this, going with one bot per server for now until there is demand for otherwise.

wraithan commented 10 years ago

Ok, going to add polyserver to the API, but not actually make the bot work with it. This may be slightly confusing but what it does is make it so you can run multiple instances of the bot that know what server they are running against, but only a single set of services. Also it means someone could make a polyserver bot that handles it all.