The signed applet is surely a simpler and more elegant solution..
In some projects however this could not be a viable option:
the "System properties problem" you have pointed out (and I had missed
:-) is hopefully going to be solved in 1.9
(http://issues.apache.org/jira/browse/LUCENE-369)
Fabio
> Wouldn't this be a good case for the JarDirectory implementation
> somebody asked for?
> The index could then be statically written in a jar file downloaded
> with the applet (the original mail refers to static offline HTML
> files).
I wrote a quick and dirty implementation of a JarDirectory - i
On Feb 20, 2006, at 12:42 PM, Fabio Insaccanebbia wrote:
Wouldn't this be a good case for the JarDirectory implementation
somebody asked for?
The index could then be statically written in a jar file downloaded
with the applet (the original mail refers to static offline HTML
files).
It could eve
Hey Dolf.
On Feb 20, 2006, at 12:11 PM, Trieschnigg, R.B. ((Dolf)) wrote:
Hi Paulo,
The main problem is that Lucene needs to store its index on a disk
which under normal circumstances an applet may not read. The applet
operates in a sandbox, which only allows "safe" operations. Reading
a
Wouldn't this be a good case for the JarDirectory implementation
somebody asked for?
The index could then be statically written in a jar file downloaded
with the applet (the original mail refers to static offline HTML
files).
It could even be a great idea for improving the Maven site-plugin :-)
[I
Hi Paulo,
The main problem is that Lucene needs to store its index on a disk which under
normal circumstances an applet may not read. The applet operates in a sandbox,
which only allows "safe" operations. Reading and writing to disk is not
allowed. An applet can only get resources from the host
