Pradeep Sharma wrote:
Still in the designing phase, and I see that we need to manage several
> user / application specific configurations and I am exploring the idea
> of storing the configuration information also in the Index, may be
> create a separate index just for the configuration, because each
> module of the application will have access to Lucene classes.
I know technically this can be done, but are there any best practises
> which discourage this?
This would make sense only if you're planning to do some kind of text
search over the configuration. Otherwise, you're better off just
keeping configuration somewhere else.
Updating a text index when a configuration element changes is a less
than pretty operation, whereas using the Preferences API is reasonably sane.
Daniel
--
Daniel Noll
Nuix Australia Pty Ltd
Suite 79, 89 Jones St, Ultimo NSW 2007, Australia
Phone: (02) 9280 0699
Fax: (02) 9212 6902
This message is intended only for the named recipient. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
message or attachment is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
