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

Multiple instance bug #132

Open
JustinChu opened this issue Apr 2, 2012 · 2 comments
Open

Multiple instance bug #132

JustinChu opened this issue Apr 2, 2012 · 2 comments
Labels

Comments

@JustinChu
Copy link
Member

When running multiple instances of our program on different machines, sometimes instances interfere with each other.

Possible fixes:

  • Cause sorting and search functions to return list of IDs to the client rather than keep them on server. May slow down application.
  • If we can guarantee that the client programs connect only to a single instance at any start up of our program on the client than we can have each instance store multiple houseID sets. These houseID sets be identified by a "setID" generated by the server. This is harder to understand/implement but it will fix the bug without compromising speed.
@JustinChu
Copy link
Member Author

The latter solution seems to be better but I am having trouble getting it to work. I have made a branch for both versions but they are currently heavly bugged.

@JustinChu
Copy link
Member Author

Another possible solution is to perform the searches every time a new page of the table is requested or sorted. This would require storing the search request information in on the client and passing it into the sort and page request functions. This will be slower than the client tracking method, but less prone to bugs. If I optimize the search functions then this implementation may become actually quite fast.

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

No branches or pull requests

1 participant