Skip to content
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

feature: client limits #311

Open
2 tasks
tablatronix opened this issue Feb 8, 2017 · 2 comments
Open
2 tasks

feature: client limits #311

tablatronix opened this issue Feb 8, 2017 · 2 comments
Labels
enhancement Feature Request

Comments

@tablatronix
Copy link
Collaborator

tablatronix commented Feb 8, 2017

might not be a good idea, but was thinking it might be wanted as globals.

  • ap user limit
  • webserver user limit

This will have to be an optional limit, however this "might" cause issues if sessions do not close out and a user is having issues and it refuses connection after dropped connections.

But it might be desirable to not allow users on ap and webserver when someone is already configuring, in case not using passwords, prevent abuse ?

@tzapu
Copy link
Owner

tzapu commented Feb 8, 2017

it's a good idea, but i think the question really is, is it worth it?
configuration is really done quite fast and people should be using a password to prevent abuse so i'm thinking there are probably other issues to tackle before this becomes a real issue

@tablatronix
Copy link
Collaborator Author

Also worth noting the web server only handles 4 sockets.

@tablatronix tablatronix changed the title client limits feature: client limits Feb 9, 2017
@tablatronix tablatronix added the enhancement Feature Request label Aug 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature Request
Projects
None yet
Development

No branches or pull requests

2 participants