When implementing the async/await paradigm it would have to be provided
as a logging event api and continuously invoked with async down to the
appender implementations in order for the application code to benefit
from true async behavior. Or am I wrong here?
On 2018-05-09 13:48, William Davis wrote:
Jochen, I dont believe that appender has been ported to Log4Net. Maybe
thats what we should do first? Im sure there are other uses cases out there
though, which is why we've seen several people roll async appenders in the
first place (although it could be a fundamental lack of understanding)
On Wed, May 9, 2018 at 7:00 AM, Jochen Wiedmann <[email protected]>
wrote:
On Mon, May 7, 2018 at 2:15 PM William Davis <[email protected]>
wrote:
I've noticed that there are several Async implementations of standard
appenders out in the wild. Is there a reason none of these have made
there
way into the core product? Is it just b/c no one has taken the time to do
a
pull request, or is there some other reason?
I wonder, why one would create a special async version, when all you need
to do is to put a standard async logger in front of the sync logger [1]?
Jochen
1: https://logging.apache.org/log4j/2.x/manual/async.html#MixedSync-Async
