[jira] [Commented] (LOG4NET-487) Control mutex type

["Dominik Psenner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4NET-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985933#comment-14985933 ] 

Dominik Psenner commented on LOG4NET-487:
-----------------------------------------

Agreed, however the configuration option should include the following possibilities:

* global mutex
* local mutex
* thread lock
* no lock

The only thing I do not like is that this is another configuration option whereas this could maybe detected from the already configured lockingmodel. What do you think?

> Control mutex type
> ------------------
>
>                 Key: LOG4NET-487
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-487
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.14, 1.3.0
>            Reporter: NN
>            Assignee: Dominik Psenner
>
> The only missing feature is an option for choosing Local (per session) or Global (per machine) mutex.
> The current code just uses the filename for mutex which good but it always makes a local one, so if you have two sessions you cannot synchronize them.
> Default is Local for backward compatibility.
> See Note in: https://msdn.microsoft.com/en-us/library/system.threading.mutex%28v=vs.110%29.aspx 
> I think it can be an option like
> <RollingMutexType value="Global" /> 
> or something like that.
> It also applies to FileAppender mutex .
> <LockingModel InterProcessLock>
>   <LockingMutexType value="Global" />
> </..>
> See issue #485 for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)