-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple channel handling #24
Comments
Pull #27 made the first steps towards this but we still need to mod a lot of the code where channels get passed around to allow for multiple channels at once. So not finished but getting there. |
Has this made any progress ,or where are we at now with this? If not, what would be the initial steps to getting multiple channels working? |
Nothing has been done in this direction. Here's what I'm thinking. In the settings, have each channel info be added as a different section of the settings (with a database per channel). So one section for #reddit-progether and another for #progether-bots, for example. Then you would start the program with python main <channel_keyword> as an arg. Each channel keyword is connected to a section in the settings. Then mainpy would start a instance of ircBot in a different thread for each channel. Each ircBot thread would only load the necessary channel information from the settings.txt. I think having a new database for each channel is probably necessary and important though that may be debated. |
Well I like the direction this is going, but should we fix the settings.txt file in the other issue first? :) |
This issue is very low priority. Especially seeing as it's only being used in one channel. |
Allow the bot to run on multiple channels concurrently.
Hopefully won't need to get into multi-threading as I've heard multi-threading is a headache in python.
Anyway, this would be useful as there are already multiple channels people are using to chat. eg #learnjava is being used for JAdventure. And I have #ProgetherBotTest open for bots
The text was updated successfully, but these errors were encountered: