This use case is met in the current code, though it requires client side filtering. Does this use case require the server to do the filtering?
There will be may cases like this, where the client application can pull over information and then do further filtering. The schema we define has impacts on the client side requirements. The client would have to have storage (memory or disk) to hold the temporary data, and the processing would be slower than if the server did the filtering. So perhaps we could add some documentation on each use case about where the filtering needs to occur.
This use case is met in the current code, though it requires client side filtering. Does this use case require the server to do the filtering?
There will be may cases like this, where the client application can pull over information and then do further filtering. The schema we define has impacts on the client side requirements. The client would have to have storage (memory or disk) to hold the temporary data, and the processing would be slower than if the server did the filtering. So perhaps we could add some documentation on each use case about where the filtering needs to occur.