Skip to content

feat: seperate client frameworks #3

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.

Sign up for GitHub

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

Jump to bottom
Open
yusdacra opened this issue Dec 21, 2020 · 1 comment
Open

feat: seperate client frameworks #3

yusdacra opened this issue Dec 21, 2020 · 1 comment
Labels
feature New feature help wanted Extra attention is needed

Comments

@yusdacra
Copy link
Member

Ideally there should be two seperate clients: one "stateless" and one "stateful", stateful one basically being a batteries included higher level API while the stateless one is for people who don't need the full stateful client (or they just want more flexibility).
@yusdacra yusdacra mentioned this issue Dec 21, 2020
Closed
@yusdacra yusdacra added feature New feature help wanted Extra attention is needed and removed enhancement labels Dec 28, 2020
@yusdacra yusdacra changed the title Seperate clients feat: seperate client frameworks Jan 18, 2021
@yusdacra
Copy link
Member Author

We could also make use of a bot framework, which should give the user to select either the stateless client or the stateful client as a backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yusdacra