Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
My impression is that logging out with the Notes client still open seems to sometimes force-quit the code that is still exiting. Just like when people use nsd like in the comment from 2020-03-04 at 10:04, that has the potential of non-graceful close-out of configuration files and databases, and corrupting them.
This corruption is very unwelcome. Mitigating this should be top priority. Especially since the desire to run Notes as PWA on a phone. To my knowledge the Phone application environment is a bit volatile, where apps can be forcefully evicted from running by the OS if the need arises. The Notes app should be resilient to this, maybe use tricks like transaction logging, and including a mechanism to safeguard the config files not in an nsf (I run the client with transaction logging on if possible since R5 for precisely these reasons. R5 Designer had a nasty habit of quitting suddenly while working on Designs. Would love tos a similar mechanism to help with the Eclipse client not clobbering one of the many configuration files)
I completely agree. Running a nsd -kill a few times a day is annoying.