-
Notifications
You must be signed in to change notification settings - Fork 197
Open
Description
What are your thoughts on extending the existing evaluation API with functionally equivalent (to POSTs) GET requests (e.g. GET /evaluation and GET /evaluation/batch)?
Several pros could be observed from general perspective (like idempotency of evaluate), but the main actual reason I'm asking is that my client feature flag request is time critical, and:
-
is always not a simple request from CORS perspective, so a preflight request is always spawned (and it is quite important for us to have an option to keep our services on different hosts for some organisational purposes);
POST /evaluation/batch ... ... Content-Type: application/json ... - there is no option to preload the request (by inlining it in the resulting client's HTML);
- GET request is more straightforward from cache control perspective (e.g. when your application shares the same feature flags across different "pages").
(at the moment we address these drawbacks at the infrastructure level: edges/lambdas, reverse proxies, etc.)
Cons are obvious I guess — URL length limitations. Any other?
Metadata
Metadata
Assignees
Labels
No labels