J
Josh Carlisle
I have a server activated .Net remoting component so it's life time is very
short. During a method call I access a configuration file (normal XML
document) to decide whether to execute a set of logic (specifically some
custom logging/auditing routines). I'm concerned with the overhead of
opening a XML document for each call to obtain these settings regardless of
whether the logging is done or not (based on settings in the config file).
I'm stuck using a configuration file but I'm curious if there is any
advice/best practices for optimally access the config file with as little
overhead as possible and additionally the most efficient way of reading the
XML data file (e.g. xmlserialized class, dataset, raw XML read, etc). I do
plan on getting some times on different methods but I thought I'd get some
advice first.
Thanks in advance.
Josh
short. During a method call I access a configuration file (normal XML
document) to decide whether to execute a set of logic (specifically some
custom logging/auditing routines). I'm concerned with the overhead of
opening a XML document for each call to obtain these settings regardless of
whether the logging is done or not (based on settings in the config file).
I'm stuck using a configuration file but I'm curious if there is any
advice/best practices for optimally access the config file with as little
overhead as possible and additionally the most efficient way of reading the
XML data file (e.g. xmlserialized class, dataset, raw XML read, etc). I do
plan on getting some times on different methods but I thought I'd get some
advice first.
Thanks in advance.
Josh