08-02-2019, 04:57 AM
Thanks!
What I'm doing is a quick snapshot of session details, so for myself I think your answer is enough. If I hit a locked session I can loop back to it at some point, nothing I'm doing with this is critical at this point. I do have some strings I'm reading, but most are unlikely to change. Doubles (TTimes in particular) for session start and last access time will be changing. Stuff like that.
Almost all is reading, though I have a "traceon" flag that I might write. It's boolean.
But, others might want to be more adventurous. An example, or doc page, might be a good thing to put on the "to do" list for some time in the future. It's unlikely I'm the only one that will want to do this stuff. Don't put aside development for it on account of me though.
Oops... one more question springs from this: If I use a session lock, and my lock is successful, will it break other session activity or will that activity wait for my unlock?
Dan
What I'm doing is a quick snapshot of session details, so for myself I think your answer is enough. If I hit a locked session I can loop back to it at some point, nothing I'm doing with this is critical at this point. I do have some strings I'm reading, but most are unlikely to change. Doubles (TTimes in particular) for session start and last access time will be changing. Stuff like that.
Almost all is reading, though I have a "traceon" flag that I might write. It's boolean.
But, others might want to be more adventurous. An example, or doc page, might be a good thing to put on the "to do" list for some time in the future. It's unlikely I'm the only one that will want to do this stuff. Don't put aside development for it on account of me though.
Oops... one more question springs from this: If I use a session lock, and my lock is successful, will it break other session activity or will that activity wait for my unlock?
Dan