Bug 69991 - Centralize access to SystemFileSystem
Centralize access to SystemFileSystem
Status: NEW
Product: apisupport
Classification: Unclassified
Component: Project
5.x
All All
: P2 (vote)
: TBD
Assigned To: Martin Kozeny
issues@apisupport
: PERFORMANCE
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-07 08:15 UTC by Martin Krauskopf
Modified: 2013-02-14 13:18 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Krauskopf 2005-12-07 08:15:03 UTC
Currently SFS is reread everytime a wizard (action, project template, wizard
wizard) starts. Could those wizards and other code accesssing SFS somehow
utilize "live" SFS kept by LayerNode? So LayerNode and other code would use
per-project instance firstly created when it is firstly needed. And maybe
garbage-collected if it not needed for sometime (e.g. was used from a wizard but
LayerNode wasn't expanded yet and other wizard wasn't ivnoked for some time).
Feel free to retake if you have time for it. I didn't take a look at the
LayerNode code too much yet.
Comment 1 Jesse Glick 2005-12-07 16:59:00 UTC
1. SFS is not recreated from scratch - pieces cached by individual modules.

2. If we introduce a cache, we have to introduce all sorts of hellish logic to
figure out when to invalidate it. I preferred to leave it a little slow than
introduce another dozen bugs.
Comment 2 Martin Krauskopf 2008-02-07 17:51:05 UTC
I'm not working on APISupport anymore. Reassigning to owner of the component, so
the issue is not 'forgotten' forever.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo