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

No separation for multiple concurrent searches #1

Open

TimCoates opened this issue Apr 28, 2013 · 1 comment

Milestone

Contributor

TimCoates commented Apr 28, 2013

If multiple searches are running in parallel, there is no mechanism for searchers to 'subscribe' to a specific search.

Probably a V0.2 rather than 0.1 requirement.

philipjohn commented Apr 29, 2013

Should be simple - just needs a foreign key adding to the locations table to indicate the search that the location update relates to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment