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.

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

Change API to use a default engine #2

Open
dlongley opened this issue Jul 12, 2017 · 2 comments
Open

Change API to use a default engine #2

dlongley opened this issue Jul 12, 2017 · 2 comments
Assignees
@msporny @dlongley

Comments

@dlongley
Copy link
Member

The API for using this library should present the solve/verify functions at the top-level via a default engine. An engines property can be exposed to allow other engines to be selectively used. Switching out the default engine at any point in the future should have no effect other than performance.
@dlongley
Copy link
Member Author

Also, the verify API should be async (return its value via a callback).

@davidlehn
Copy link
Member

Also consider security concerns of loading the API via a string:
7dd8d17#r32812169

davidlehn referenced this issue Mar 19, 2019
@msporny @davidlehn
Add initial implementation.
7dd8d17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msporny msporny

@dlongley dlongley

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@msporny @davidlehn @dlongley