> > > One thought that occurred to me since yesterday: Since parsing
> > > a record from the document database depends on config values,
> > > it might be better to use an object-oriented design where
> > > "parse_docdb" is a method of a Config object.
> >
> > That sounds like a good idea to me, but I would defer to
> someone more
> > involved in the work on that part of htdig.
>
> I was thinking that I might inherit from your HtDig::Config module.
> Have you gotten far enough to say anything about the methods it
> will provide? Also, the code I wrote for parsing a config file
> doesn't amount to much, but if it's any help, feel free to borrow
> what you can use.
Thanks. What I've got so far is available on sourceforge's web site at this
URL: http://sourceforge.net/project/?group_id=970
Click into the CVS respository area and you can browse the source code. You
can also download it using anonymous CVS.
Right now, the Config module is for maintaining a registry of conf files.
It doesn't do any parsing of them, but simply keeps track of them. The Site
module is the one that parses them. Each Site object instance represents
one configuration file, and will be able to update its file upon request, or
even create a copy of it under another name. It will also be able to
initiate digs and database merges, and probably other admin-type things,
too.
A cgi subdirectory should appear in the repository tonight that contains
some preliminary CGI wrappers for these modules. The CGI system will be
very template and style-sheet oriented.
Let me know what you think!
Jamie
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
