Talk:CacheForModularity

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(Comment provided by Matteo Di Giovinazzo - via ArticleComments extension)
Line 24: Line 24:
--[http://www.streamsim.com/ Matteo Di Giovinazzo] 18:46, 20 July 2009 (CEST)
--[http://www.streamsim.com/ Matteo Di Giovinazzo] 18:46, 20 July 2009 (CEST)
</div>
</div>
 +
 +
Hello Matteo. Thanks for your talkback. The user settings are usually stored on [[NetBeansLayers|system filesystem]]. It should be easy to store this filesystem on shared server while keeping the caches locally. [[wikipedia::Nokia|Nokia]] [http://www.netbeans.org/community/articles/nokia-netact.html did it] with its [http://hg.netbeans.org/main/contrib/file/9f2e628b07a8/zeroadmin zero admin] module.
 +
 +
--[[User:JaroslavTulach|JaroslavTulach]] 16:17, 24 July 2009 (UTC)

Revision as of 16:17, 24 July 2009

Comments on CacheForModularity <comments />


Matteo Di Giovinazzo said ...

Hi Yarda, is there a way to have the location of the JAR cache different than the location of user settings?

This because we want to support an installation with a scenario like this: - RCP application installed in a server (a single installation done by the system administrator) - user settings in the same server (they will be shared among machines, so the user can log in from every machine)

Then I suppose the best location for cache will be local. The updates via NBMs will be installed local as well, since the RCP installation is read-only for all users.

But we do want to have the user settings in a network disk where the user homes reside.

Do you have any good advice?

Thanks a lot in advance!


--Matteo Di Giovinazzo 18:46, 20 July 2009 (CEST)

Hello Matteo. Thanks for your talkback. The user settings are usually stored on system filesystem. It should be easy to store this filesystem on shared server while keeping the caches locally. Nokia did it with its zero admin module.

--JaroslavTulach 16:17, 24 July 2009 (UTC)

buy