Hi all,
There have been several posts regarding startup time and how long it
can take for NHibernate to initialize a session configuration. About
a week ago Sandor D. made a change to the NHibernateSession class and
mentioned an article by Ayende Rahien regarding caching the NH
configuration (
http://msdn.microsoft.com/en-us/magazine/
ee819139.aspx). This prompted me to dig out some code from a previous
project based on the same article, and to work with Sandor to
incorporate his code into a configuration caching feature.
I've posted the new code at
http://github.com/sonomofo/Sharp-Architecture/commits/NHConfigCache.Injection.
If you are interested, please check it out and provide suggestions.
I do have several questions of my own about the code:
1) Location of the cache file. Some servers are locked down to allow
read-only access to the web applications files, so I chose a temp
folder, which points to the user account under which the web browser
is running. How would this be affected by running the app in IIS, in a
medium or low trust environment?
2) While I did add a unit test that adds a second database
configuration, and it does produce a second cache file, I don't know
how realistic of a test this is.
3) Is there any way to really unit test the actual creation of the
configuration cache file and if it can be deserialized and used
properly?
4) This has only been tested using WinXP SP3, Cassini Web Server,
VS.Net 2008 SP1, SQL Server 2008, .Net 3.5 SP1, but hey, what could
possibly go wrong!
Regards
Dan
--
You received this message because you are subscribed to the Google Groups "S#arp Architecture" group.
To post to this group, send email to
sharp-arc...@googlegroups.com.
To unsubscribe from this group, send email to
sharp-architect...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sharp-architecture?hl=en.