Originally posted by Edwin Dalorzo:
But it is my impression that implementing an exact search on the server side is the best solution. First, the servers typically have more resources to execute this complex operations, and plus, exact filtering would imply less records have to be sent over the network.
Thanks Edwin, for your reply
I'm still in doubt. My first idea was indeed to put it on the server side. Because it feels like a hassle if you have to feed the criteria first at server side to get a list of rooms, and then again feed the criteria at the client side to filter the exact matches.
However, actually reading your messages makes me doubt
Why would you want to put it on the server side? To my opinion, network traffic cannot be a serious point. As the search function has an "all" option, it is apparantly not a problem to send all records of the database over the network. Apparantly the database is not so big that we are to expect thousands of records, so this network traffic issue is really peanuts, to my opinion. And as sets are apparantly small, server load is also not an issue.
For now, I'm tending more towards bringing it to the tableModel level.. But still doubting about what is the best.
Rinke