Stream: subscriptions
Topic: Client and Server delays
Jenni Syed (Jan 12 2019 at 18:40):
Not the best topic title, but essentially, two scenarios:
- I as a server do not want to notify 10 times within a millisecond about the same change. It's unclear if it's ok for a server to "batch" up changes. EG: only alert every 10 minutes etc...
- I as a client only care about updates every hour, day, week, ... there is no way to do this today via subscription definition. IE: please don't spam me! :)
Have there been any thoughts around this?
Grahame Grieve (Jan 12 2019 at 19:05):
not to my knowledge
Jenni Syed (Jan 13 2019 at 15:48):
Thinking through this, if the client can define their interval, it gets very complicated server side to track what needs to be alerted when.
Yunwei Wang (Jan 13 2019 at 15:57):
As a client, the 2nd bullet point is very important. Will that be on the consideration?
Jenni Syed (Jan 13 2019 at 16:05):
updating from offline: If a client only wants notifications every 24 hours or so, then there's a query they can run using the lastUpdated parameter (asking what has changed since X time)
Grahame Grieve (Jan 13 2019 at 21:09):
y. we should not try supporting the client specifying the time
Brian Postlethwaite (Jan 14 2019 at 16:40):
If client wants to specify the time, that's a pull to me.
Brian Postlethwaite (Jan 14 2019 at 16:44):
If the content doesn't change, I'm ok with that not sending a notification - but then if the version number changes/and last mod date, then I think I'd want to hear about that (as it might be a trigger for other things - such as kicking off a verification process or other workflow
Last updated: Apr 12 2022 at 19:14 UTC
