You should only use the documented, public groups API - anything else will
vary based on the backend you use. You will, indeed, need your own
expiration logic and backend for this process stuff - an easy entry point
would be one of:
- A database row per process with a timestamp bumped using keepal
On Friday, 2 June 2017 14:08:40 UTC+10, Andrew Godwin wrote:
>
> I don't have any direct examples to hand - and this sort of thing does
> come all the time, but much like Django is not in the business of including
> a full CMS, Channels can't add lots of high-level features without really
> narr
I don't have any direct examples to hand - and this sort of thing does come
all the time, but much like Django is not in the business of including a
full CMS, Channels can't add lots of high-level features without really
narrowing the usage - it's a general framework for you to build something
on.
On Friday, 2 June 2017 13:04:48 UTC+10, Andrew Godwin wrote:
>
> You can't do what you ask with the current Groups system - it is
> deliberately very simple as anything more complex involves picking scaling
> tradeoffs that are particular to the thing it's powering. You'll have to
> layer some o
You can't do what you ask with the current Groups system - it is
deliberately very simple as anything more complex involves picking scaling
tradeoffs that are particular to the thing it's powering. You'll have to
layer some of your own code on top of groups (you can keep groups for the
broadcast me
5 matches
Mail list logo
