[
http://issues.ops4j.org/jira/browse/PAXLOGGING-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11390
]
Niclas Hedhman commented on PAXLOGGING-30:
------------------------------------------
The problem is not so much of "reading" vs "adding" to a buffer, but the fact
that many threads can add to the buffer simultaneously.
Since we can't rely on Java5 memory model semantics of "volatile", I can't
figure out a better way and synchronize is inevitable. Suggestions are welcome.
> Replace synchronized access to log entries buffer
> -------------------------------------------------
>
> Key: PAXLOGGING-30
> URL: http://issues.ops4j.org/jira/browse/PAXLOGGING-30
> Project: Pax Logging
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Alin Dreghiciu
> Assignee: Niclas Hedhman
> Priority: Minor
>
> PAXLOGGING-29 solution forced an synchronized access to log entries buffer.
> As the common use of logging is to log not to read the entries via a log
> reader we better "sacrifice" consistency of the buffer in favor of better
> performance by implementing a solution that is not synchronized.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
