Currently, each time a tag is selected or unselected, a PATCH streams/ request is sent to the server with the new list of tag filters. This leaves open the possibility of a user rapidly tapping items on and off which would potentially cause overloading issues or odd behavior on the server. The client should prevent this behavior.
Two possible fixes are:
Put some kind of timer on the sending of the requests to the server so only one can be sent per few seconds.
Move the request triggering from the tag selection to the button that returns the user to the Listen screen. In this case, the button returning users to the Listen screen should say something like "Done" or "Apply" to suggest the user's selections are not applied until the button is pressed.
I am fine with either method at this point. If they require equal effort, the latter is probably more sensible overall, but there are arguments for both.
Currently, each time a tag is selected or unselected, a
PATCH streams/request is sent to the server with the new list of tag filters. This leaves open the possibility of a user rapidly tapping items on and off which would potentially cause overloading issues or odd behavior on the server. The client should prevent this behavior.Two possible fixes are:
I am fine with either method at this point. If they require equal effort, the latter is probably more sensible overall, but there are arguments for both.