Re: [misterhouse-users] Re: As we approach v3.00

[Amy <w_h...@co...>]

Did a little thought refinement.  here is what i have so far:

rules:
limit to just outputting data from misterhouse. no reliance on input for
misterhouse to work.
ability to output all data.  logs,variables,object states....
all done through DBI

proposed flowchart:
one central script that has objects for optional logging.(error log,callerid
log, print log, mp3, mh global variables.......)
each of these objects could be set to on or off and would correspond to a
table in dbi_database
could also have max_entries_for_logs object and do some db cleanup with this
script
if log object on, would check that table exist and is in proper format. if
not return suggestions (haven't figured out how to make table with dbi)
if this data could easily be gathered with "central" script then do so.
if not make a snippet to put into the proper code file for logging.
(call_log.pm for callerid)
each of the logging subroutines (whether local or in some other script)
would check to make sure dbi is available and if its log object set to 'on'

concerns:
is there a better way? If it did not rely on insertion of so may little
snippet into other code files i would have less trepidation. would love to
hear some opinions before i charge ahead

just for the record, i am stuck at home for the weekend with no wife and
kids, if you are wondering "why does this guy keep posting so much?"
dave


----- Original Message ----- 
From: "Bruce Winter" <wi...@ch...>
To: <mis...@li...>
Sent: Friday, December 31, 2004 12:41 AM
Subject: Re: [misterhouse-users] Re: As we approach v3.00


> Amy wrote:
> > can't help but revisit this issue after recent 'using mysql' post.   did
> > some digging last night.  I was looking for a few key places that we
could
> > "divert" data to mysql without having to modify every code module.
looks
> > like 'logit' in handy_utilities.pl  is used to make every *.log file.
we
> > could add a few lines in this sub
> >
> > we could have a table for each log.  phone, server, print,
router........
> > then just translate $log_file to proper table and put in $log data.
> >
> > that is a huge amount of date for very little coding effort.
> > ofcourse it only puts data in and it only does the logs. but we would
have
> > to start somewhere.
>
> I think having an option of pumping out various data out to SQL would be
> nice, but it would have to be an option, not a requirement.
>
> I would use SQL (or similar database) much more extensivly if it were
> installed by default on most platforms.   Requiring it to be installed
> to get mh running would slow down an already slow installation/learning
> process.
>
> But if it were coded as optional logging (maybe if dbi_driver is
> enabled), then I'm all for it!
>
> Bruce
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> ________________________________________________________
> To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365
>
>