I decided that it's just not worth it to have an application that
needs updates to map support groups to request filters -- it's not
supposed to be that complex. Instead, the user will select their own
request filter from a drop down/combo box. I'll keep all queries
running under a service account, and remove the "My xxx
Requests" and "Requests xxx me" filters from the list.
Another solution would be to get all requests one by one and check against the group parameter. But the traffic generated by hundreds of users each querying hundreds of requests every minute makes that solution prohibitive.
REST API needs work. The only aspect the API exhibits of a RESTful design is statelessness. The request responses have too much variation in schema -- you can't deserialize an error in the same way as you deserialize a valid result! and it needs a recursive where-clause structure for complex query support [Group = 'xxx' AND (Status = 0 OR Status = 1)]. I'd just start over with a /sdpapi2/ and use JSON.
Another solution would be to get all requests one by one and check against the group parameter. But the traffic generated by hundreds of users each querying hundreds of requests every minute makes that solution prohibitive.
REST API needs work. The only aspect the API exhibits of a RESTful design is statelessness. The request responses have too much variation in schema -- you can't deserialize an error in the same way as you deserialize a valid result! and it needs a recursive where-clause structure for complex query support [Group = 'xxx' AND (Status = 0 OR Status = 1)]. I'd just start over with a /sdpapi2/ and use JSON.