You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
When running multiple instances of our program on different machines, sometimes instances interfere with each other.
Possible fixes:
The text was updated successfully, but these errors were encountered: