ra-at-diladele-com
commented
1 year ago The problem with debugging targets as of now is:
- debugger is created at the time of session start - i.e. at the time of client connect
- so at that time we of course do not know what domain the client will connect to - we will know it for example ONLY after a CONNECT request is parsed
So 1 possibility is then:
- make the debugging subsystem exclusive - i.e. admin enables dump of sessions and sets the list of domain names with verbose debugging targets. Thus if verbose debugging target is set - we ONLY dump extended info for that target; for other targets the initial session creation is dumped, nothing else.
Or 2 possibility is then: we can make the debugger a little more dynamic - i.e. it is created always and starts dumping ONLY after the target is known. If target is not known - the dumped strings are discarded and do not get on disk.
Finally we can leave it all as is and DO NOT change anything. In this case if admin wants to dump sessions - he will dump them all.
see if we can have the list of domain names for which we write sessions anyway - not when [x] write sessions is on. This can be useful to see on the live system why a given page always cannot be loaded.