Dec 17, 2025, 3:37:36 AM
|
Sweet Home 3D Forum » List all forums » » Forum: Developers » » » Thread: Debug & sweethome3D.min.js » » » » Post: Re: Debug & sweethome3D.min.js |
Print at Dec 17, 2025, 3:37:36 AM |
| Posted by Puybaret at May 29, 2023, 11:07:50 AM |
|
Re: Debug & sweethome3D.min.js It depends. From a production point of view, a Tomcat server is costly. At present time, each time a user modifies something in the house, the writehome.jsp process is launched. This is a quite huge machinery for doing almost nothing. So, with 10 users at the same time, I'm not sure the server will survive the heavy load. It doesn't require so much power on a server (by the way, to avoid confusion, the page is not writehome.jsp but writeHomeEdits.jsp). There have been already more than 250 user sessions at the same time on sweethome3d.com server with 10 calls to writeHomeEdits.jsp per second peaks and the CPU load kept low. The good thing is that you may restart the JSP server without breaking the update process. Moreover, some users do not really want their data to stay on an unknown server. I recommend to these users to use the Desktop version, even if they will have also to trust the installer too. The Privacy policy clearly states that homes data created with Sweet Home 3D application installed on a user's computer is only stored on his or her computer.If the user wants to save his plans every 5 minutes, it will create a new file in the download directory. Ok, not really sexy, but not really problematic. I find this is really not ergonomic. Sweet Home 3D doesn't target only computer users with good knowledge about how browser downloads are stored. Anyway, I'll probably add a JavaScript export function that will save current home in a blob that can be saved in download directory. ---------------------------------------- Emmanuel Puybaret, Sweet Home 3D creator |
|
|
Current timezone is GMT Dec 17, 2025, 3:37:36 AM |