If anyone at Hasura is reading this. Are there any plans to make poll frequency configurable on a per-query basis?
We have different queries with dramatically different latency requirements (e.g. 1 second vs 5 minutes vs 1 hour). Currently we are only using Hasura for the low-latency queries, and are falling back to polling for other things. But it would simplify our development model if we could just subscribe to these changes with a lower frequency.
If we could additionally have some kind of ETAG-style if-not-modified support when initialising connections, that would be extra amazing.
@nicoburns: Yes, this is something that we've been thinking about, but we haven't put a spec together yet.
Could you open a github issue with a rough proposal of how you'd like to specify this information?
For example: at a subscription level (with a directive or header), or via metadata built-on query collections [1] (what Hasura uses underneath for managing allow-lists).
This feature is available with WunderGraph. You can configure Auth, caching, live query polling etc. at a global level and override it for each individual query:
Looks like you are associated with wundergraph( based on your posting history here). Would you mind making that clear in your post given you are posting on a competitors HN post.
We have different queries with dramatically different latency requirements (e.g. 1 second vs 5 minutes vs 1 hour). Currently we are only using Hasura for the low-latency queries, and are falling back to polling for other things. But it would simplify our development model if we could just subscribe to these changes with a lower frequency.
If we could additionally have some kind of ETAG-style if-not-modified support when initialising connections, that would be extra amazing.