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

Implement matching backend #12

Closed
nirizr opened this issue Aug 14, 2016 · 3 comments
Closed

Implement matching backend #12

nirizr opened this issue Aug 14, 2016 · 3 comments
Assignees
@nirizr
Milestone
first-release

Comments

@nirizr
Copy link
Owner

nirizr commented Aug 14, 2016

We need to implement the server side matching backend, actually generating match results for provided data.
@nirizr nirizr added this to the first-release milestone Aug 14, 2016
@nirizr
Copy link
Owner Author

nirizr commented Aug 15, 2016 •
edited
Loading

  1. Should this be client or server side?
  2. Should we use Celery or something simpler if server side?
  3. Is dask a valid option here?
  4. Should we avoid 3rd party libraries such as numpy in client side (due to IDA's inability to handle package dependencies / pypi)?

@shiftre
Copy link
Collaborator

shiftre commented Aug 20, 2016

  1. Both imo.
  2. I don't know.
  3. Yes, backend.
  4. Clientside yes, at least in early stages.

@nirizr nirizr self-assigned this Aug 22, 2016
@nirizr
Copy link
Owner Author

nirizr commented Nov 8, 2016

Done! #22

@nirizr nirizr closed this as completed Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nirizr nirizr

Labels
None yet
Projects
None yet
Milestone
first-release
Development

No branches or pull requests
2 participants
@shiftre @nirizr