Channel/connection persistence between restarts and other fun fixes #131

Merged
merged 2 commits into from Jul 2, 2012

Conversation

Projects
None yet
2 participants
@ericbarch
Collaborator

ericbarch commented Jul 2, 2012

Hoping to get more actively involved in the development of Subway. I'm currently in the process of building out enough functionality to be able to drop my ZNC bouncer for Subway.

These commits include the scrollable channel list, wrap fix for channel names, mongodb models broken out into a separate file, channel/connection persistence between subway restarts, storing logs based on server/user, fix for nick changing, and an issue with case sensitivity/channel names.

ericbarch added some commits Jul 2, 2012

Mongodb models broken out into separate file, persistence of a user's…
… connection and the channels they join part (similar to IRC bouncer behavior). Fixed changing of nick. Fixed channel case sensitivity.

thedjpetersen pushed a commit that referenced this pull request Jul 2, 2012

David Petersen
Merge pull request #131 from ericbarch/master
Channel/connection persistence between restarts and other fun fixes

@thedjpetersen thedjpetersen merged commit 9e283c5 into thedjpetersen:master Jul 2, 2012

@thedjpetersen

This comment has been minimized.

Show comment Hide comment
@thedjpetersen

thedjpetersen Nov 26, 2012

Owner

I am thinking about dropping the Connection model is there particular reason it needs to be there? @ericbarch

Owner

thedjpetersen commented on aa85ce9 Nov 26, 2012

I am thinking about dropping the Connection model is there particular reason it needs to be there? @ericbarch

This comment has been minimized.

Show comment Hide comment
@ericbarch

ericbarch Nov 26, 2012

Collaborator

Hmm, are you proposing moving the fields that are in there to the users model? The original thought behind that was so we could support multiple IRC server connections per user login. I suppose this is really a fundamental question regarding Subway's goal as a project. Focus on bouncer functionality for auth'd users or an excellent replacement for web IRC clients? For me I was most interested in implementing the bouncer side of the project so that I could replace ZNC/Irssi. Thoughts?

Collaborator

ericbarch replied Nov 26, 2012

Hmm, are you proposing moving the fields that are in there to the users model? The original thought behind that was so we could support multiple IRC server connections per user login. I suppose this is really a fundamental question regarding Subway's goal as a project. Focus on bouncer functionality for auth'd users or an excellent replacement for web IRC clients? For me I was most interested in implementing the bouncer side of the project so that I could replace ZNC/Irssi. Thoughts?

This comment has been minimized.

Show comment Hide comment
@thedjpetersen

thedjpetersen Nov 26, 2012

Owner

@ericbarch I am fine with subway being used either way(as a webclient or a bouncer, or in some cases both). I am working on migrating from mongodb to sqlite. I hadn't dug into the backend code for a bit so I was wondering what the purpose of the connection model was.

Owner

thedjpetersen replied Nov 26, 2012

@ericbarch I am fine with subway being used either way(as a webclient or a bouncer, or in some cases both). I am working on migrating from mongodb to sqlite. I hadn't dug into the backend code for a bit so I was wondering what the purpose of the connection model was.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment