meinc wrote:
Hi all,
I need some help and advice on deployment of felix based desktop
applications.
We intend to use felix for a typical swing desktop application which is
installed on a single computer for multiple users. Even a single user may
start the apllication more than once.
1.) Would it be save to share a single felix cache profiledir for several
instances of the application
No, this is not safe. You would be better off somehow having your
launcher detect if your app was already running and if so, tell it to
create a new window. Thus, all "instances" come from the same running
instance. I think you will use less memory this way too.
I already tested to share the profile and it seems to work. However since
the cache does not distinct between bundle install and bundle state
locations I'm afraid of blocking write operations that reflect state changes
2.) Is it reasonable to distribute a preconfigured felix cache profiledir
rather distribute the bundles and let felix do the initial cache setup.
I'm asking these questions since we have to integrate a third party archive
which has a size of about 80 MB and we don't want this OSGified jar copied
to multiple profiles.
Yes, it is perfectly reasonable to have a preconfigured felix bundle
cache. Another approach is the one that Karl suggests.
-> richard
Regards
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
