When looking through the log4net source code I noticed there was duplicate code in all the classes that extend LockingModelBase. I mentioned in passing that a better place for that code would be in LockingModelBase. I haven't heard of anyone every extending LockingModelBase classes so its not a priority item as far as I'm concerned.
In your case it would make it very easy to control how the FileStream is created. You could extend one of the existing locking model classes and override one method; namely CreateFileStream. If you think you or other people would benefit from this go ahead and create a JIRA ticket for it. Its still possible to control how the FileStream is created...its just not as easy. My ReadWriteTextWriterAppender class was an example of how you have to do things today by creating the QuietWriter yourself. ----- Original Message ---- From: Frogg <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, April 16, 2007 2:34:51 PM Subject: Re: FileAppender ExclusiveLock workaround (Not MinimalLock) Hi Ron, Thank you for your reply. I am not sure how to proceed with your suggestion. Are you suggesting to add a method in LockingModelBase and recombile log4net or extend LockingModelBase and add this method in that subclass? Thanks, Ryan
