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

Flask compatibility #4

Open
WernerWildenboer opened this issue Aug 15, 2019 · 1 comment
Open

Flask compatibility #4

WernerWildenboer opened this issue Aug 15, 2019 · 1 comment

Comments

@WernerWildenboer
Copy link

Probably a stupid question just want to know if this is possible or not, if so how would that be done

@alexmojaki
Copy link
Owner

It looks like it's currently not possible.

It might be better (for this issue and others) if the heartrate server lived in its own process and was run separately, instead of just in a thread in the same program. The problems are that:

  1. It would be less convenient for users to run the server separately.
  2. It's a lot more work to implement, particularly the communication between the heartrate server and the traced program, e.g. over a database. This library was an idea that I thought would be fun to hack together quickly, and it's getting more attention than I expected. I need to be convinced that it's actually useful to people and worth putting effort into. I don't actually use it myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants