diff options
Diffstat (limited to 'apps/JAWS/server/README')
| -rw-r--r-- | apps/JAWS/server/README | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/apps/JAWS/server/README b/apps/JAWS/server/README index 27f0a0e3a8d..4fab66d703d 100644 --- a/apps/JAWS/server/README +++ b/apps/JAWS/server/README @@ -21,8 +21,6 @@ CONTENTS 4. Acknowledgements -5. New additions - ------------ 1. Compiling ------------ @@ -201,28 +199,3 @@ James Hu <jxh@cs.wustl.edu> Tim Harrison For his comments, advice, and help in designing the IO mechanism used by JAWS. - ------------------------ -5. Additions ------------------------ - -The need arose to have JAWS not perform any file caching. We added this -functionality and provided a new cmd line option -c with params NO_CACHE/CACHE. - -This capability is to be used with the RepositoryManager in CIAO. - -In its current design the RepositoryManager (RM) need a collocated HTTP server. -When RM istalls packages, it unpacks them so that the separate files are accessible to -ZIP unaware entities like JAWS. JAWS is used to serve the libraries in the package to the -various deamons that might be interested in them, e.g. the NodeApplicationManager. - -The problem with using file caching reveals itself during the deletePackage operation of -the RM. When the RM attempts to delete a file which was previously accessed via JAWS a -is currently in the file cache the call fails and the file remains on the filesystem -indefinitely. If the file is cached with a ACE_NOMAP option is is not stored in a file -map and it is deleted upon server termination. The OS handles that. Althoguh this might -or might not be OK (depending on how it scales) there is an additional problem because -JAWS and the ACE_Filecache_Handle class used do not provide enough functionality to deal -with the ACE_NOMAP case. I believe that ACE_NOMAP option was probably never used. - -To overcome the above problems we added the no caching functionality in JAWS. |