...
- On logout → this would not support the "remote developer" case
- Explicit hard limit
- Default value at system or per-spec
- Inactive for some predetermined period
- How would we measure inactivity?
- HTTP → monitor ingress rules
- WebSockets → open WebSocket connections
- TCP → ???
- How would we measure inactivity?
Requirements for Beta:
- Since resource contention will be lowest in beta, we will likely not need to worry about this before the beta release
- We should definitely warn our users of our plan to institute such a policy before carrying it out on the beta
- If there's time, we will impose a system-level explicit hard limit (likely 2 or 4 hours)