Normal
about log4net.. we really need this in tve3.5 as well as in tve3.5@mp2 about logging performance, how does it work behinds the curtains ?ideally it should be an "in memory queue" of log items.then a threaded static logger class would pop those queued log items and commit them to disk, one at a time.this would make calls to log very cheap performance wise. so an encapsulation of log4net would be needed here. I've already done similar work for an asynch mailer class at work.send mail to queue and process it in a thread, then dispatch mails one at a time.could easily be modded to take care of logging instead of mailing. /gibman
about log4net.. we really need this in tve3.5 as well as in tve3.5@mp2
about logging performance, how does it work behinds the curtains ?
ideally it should be an "in memory queue" of log items.
then a threaded static logger class would pop those queued log items and commit them to disk, one at a time.
this would make calls to log very cheap performance wise.
so an encapsulation of log4net would be needed here.
I've already done similar work for an asynch mailer class at work.
send mail to queue and process it in a thread, then dispatch mails one at a time.
could easily be modded to take care of logging instead of mailing.
/gibman
