Hi Stjepan,
On Montag, 15. Dezember 2008, Stjepan Gros wrote:
> On Sun, Dec 14, 2008 at 9:58 PM, Jan-Oliver Wagner
> > Wouldn't another solution option be to reorganize the caching as such
> > to be based on OIDs instead of names?
>
> That is the idea. The problem is that plugins themselves, as source
> files, are stored in files with descriptive names. Now, when you know
> the name of the plugin on a disk, you don't know it's OID until you
> read and parse it.
>
> For easier understanding I'll describe this process now, and how it is
> planned to be implemented, on a plugin named plugin.nasl with an OID
> 1.2.3.4.5.6.7.8
>...
>
> Did I better explain the problem?
yes, that helped me to make up my mind:
It is probably best to have the cachedir be a 1:1 mirror of the
plugindir:
$PLUGINDIR/script.nasl
is cached to
$CACHEDIR/script.desc
and in the future:
$PLUGINDIR/script.nasl
$PLUGINDIR/myfamily/script2.nasl
to
$CACHEDIR/script.desc
$CACHEDIR/myfamily/script2.nasl
The background idea is to not invent a second organizational structure,
but rather use the same one.
Best
Jan
--
Dr. Jan-Oliver Wagner | ++49-541-335 08 30 | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
