hadmut commented on issue #5411: URL: https://github.com/apache/couchdb/issues/5411#issuecomment-2632143502
Oh, it doesn't mean to restart it for every single request. And it doesn't mean terminating after a connection. Once started, it should run for a given time period after last use. But if you do use CouchDB only occasionally, as I do, why should it consume memory, boot time, battery power, if it isn't used most of the time? After all, I am just asking for supporting it, not for enforcing it, thus leaving the decision to the admin. Especially for a non-centralized structure as couchdb has, it makes sense to start couchdb (e.g. on desktop machines, notebooks, ...) only if actually needed, and not on every boot. And, btw., that's what good 'ole inetd or modern systemd socket activation is made for. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
