Abstract sockets from being a part of the bot framework #8

Open
opened 2018-10-16 15:38:22 +00:00 by aewens · 0 comments
Owner

The bot could more easily recover from errors if it wasn't responsible for handling the socket connection. This could allow for the bot to be started cold and given a clean socket to work with, or have it dump it's data and pass the socket connection over to a new instance of the bot if anything buggy occurs (e.g. being overloaded with tasks to run).

By extension, this could allow for the possibility of the bot to pull in updates for it's code and restart itself without ever dropping from the IRC (neat!).

The bot could more easily recover from errors if it wasn't responsible for handling the socket connection. This could allow for the bot to be started cold and given a clean socket to work with, or have it dump it's data and pass the socket connection over to a new instance of the bot if anything buggy occurs (e.g. being overloaded with tasks to run). By extension, this could allow for the possibility of the bot to pull in updates for it's code and restart itself without ever dropping from the IRC (neat!).
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: aewens/babili-bot#8
No description provided.