Currently, if a user sends two identical requests to ClientService, it will only make one request and send the same result two both promises. There are situations where the user may want to actually make two identical requests, so this behavior should be made configurable.
The easy way would be to make it a Boolean, with default set to true. However, the original intent was to be a poor man's caching mechanism (application sends two identical GET requests, just burden the server with one request since it would be likely returning the same result); it may be better to have the default functionality be to group identical GET requests, but don't group identical requests that aren't GET (i.e. POST). This would require a more complex configuration mechanism.
Currently, if a user sends two identical requests to
ClientService, it will only make one request and send the same result two both promises. There are situations where the user may want to actually make two identical requests, so this behavior should be made configurable.The easy way would be to make it a Boolean, with default set to true. However, the original intent was to be a poor man's caching mechanism (application sends two identical GET requests, just burden the server with one request since it would be likely returning the same result); it may be better to have the default functionality be to group identical GET requests, but don't group identical requests that aren't GET (i.e. POST). This would require a more complex configuration mechanism.