Well, I guess that answers my question.
It's just that the explanation about the motivation for using Akka's
logging ignores the fact that very large portions of the system could be
unaware of running inside an actor system, which means the performance
benefit of using Akka's logging is quite limited.
The more classes you have that are unaware of running inside an actor
system, the more classes you have that use standard logging facilities
which in turn means using locks, extra threads etc.
I was hoping to find a way to shed that extra weight, but I guess there
isn't one for now.
Thanks.
On Monday, June 23, 2014 6:55:19 PM UTC+3, Björn Antonsson wrote:
>
> Hi Adam,
>
> I'm not sure that I understand your question completely.
>
> Akka can use slf4j as a backend for akka logging. Akka does not provide a
> generic slf4 backend that uses an akka actor system.
>
> In your akka code you can use akka logging and in your other code you can
> use slf4j, and the logging can be combined with the help of the akka-slf4j
> mdoule.
>
> B/
>
> On 22 June 2014 at 10:01:52, Adam ([email protected] <javascript:>) wrote:
>
> Hi,
>
> I've read thorough the instructions under the logging chapter of the Akka
> manual(Java API in this case) and it seems like what it requires is
> directly using the akka.event.Logging and akka.event.LoggingAdapter
> classes.
> (BTW Suspecting I might have missed something in the documentation, I
> looked for a StaticLoggerBinder class inside the akk-slf4j jar, but
> couldn't find one.)
>
> So I'm wondering if there's a way to avoid this and only use the SLF4J API.
> My motivation for doing this is:
>
> 1. I'll have a single logging API used throughout the application
> 2. SLF4J actual implementation can be replaced more easily than when
> having Akka hard-coded everywhere.
> 3. Other parts of the application which may not even be aware of
> running inside an Akka actor system and are already using the SLF4J API,
> will automatically be switched to using the AKKA implementation.
>
> As it currently stands I can only make parts of the application use Akka
> logging, while other parts will use some other logging framework's
> asynchronous logging and all which that entails (extra threads, locks, etc.)
>
>
>
> --
> >>>>>>>>>> Read the docs: http://akka.io/docs/
> >>>>>>>>>> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> To post to this group, send email to [email protected]
> <javascript:>.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> *Björn Antonsson*
> Typesafe <http://typesafe.com/> – Reactive Apps on the JVM
> twitter: @bantonsson <http://twitter.com/#!/bantonsson>
>
>
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
