<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Replace Quickstarter by taking advantage of the Windows native "always running" startup method"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=116694#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Replace Quickstarter by taking advantage of the Windows native "always running" startup method"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=116694">bug 116694</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=116694#c3">comment #3</a>)
<span class="quote">> Sure either shell:startup or the registry HKCU or HKLM CurrentVersion\Run
> keys can be laid down by the MSI.</span >
... and after installation, user can enable/disable the Quickstarter from the
UI, without the need to re-run the installer.
There's ~no overhead here. The implementation doesn't restart processes: it
reinstalls the icon into the tray, while still running the process. This
*removes* additional overhead of running *separate* process as service: no
additional memory or CPU requirements, no IP communications across system
security borders (system-to-user), no counting of possible concurrent user
sessions (with different users soffice running - usual, e.g., on terminal
services), no additional development overhead of managing (changing security
requirements) etc.
So - I don't see any additional overhead to implement *existing* functionality.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>