[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322196#comment-15322196
]
Anthony Maire commented on LOG4J2-1397:
---------------------------------------
I agree that this is a narrow use case
Another possible approach is to let the user inject it's implementation of the
ringbuffer slot factory (and provide the method to transfer data from the
application thread to the ringbuffer slot, then from the slot to the background
thread). Does it seems OK to you ?
Basically all use cases where the user want to access parameters at the
appender level (background formatting, custom filters ...) are potentially
broken with async logger if these parameters are mutable. And it will almost
always be narrow use cases. I think that it can be a good solution to let the
user a way to copy the piece of data that need to be copied for its use case
> Support ByteBufferLayout
> ------------------------
>
> Key: LOG4J2-1397
> URL: https://issues.apache.org/jira/browse/LOG4J2-1397
> Project: Log4j 2
> Issue Type: New Feature
> Components: Layouts
> Affects Versions: 2.6
> Reporter: Remko Popma
>
> As requested by Kirk Pepperdine on the Mechanical Sympathy [mailing
> list|https://groups.google.com/d/msg/mechanical-sympathy/klefjRqlpQE/-1WF59IGAwAJ]:
> Support a new Layout that takes ObjectMessages containing a ByteBuffer
> payload and write them to the appender without modification.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
