fluent-logger-java
fluent-logger-java copied to clipboard
enable some asynchronous logging (revised)
Revised #30.
And I modified setErrorHandler/removeErrorHandler
in AsyncRawSocketSender
.
Should I add tests for AsyncRawSocketSender
?
Why does this feature make no progress anymore?
This feature is implemented in Fluency. I think that this library's owners do not want to add this feature because they want to keep simple implementation.
@cosmo0920 Oh really sorry, I failed to notice the notifications of this project. Let me see the changes.
@cosmo0920 @mxk1235 Thanks for the PRs! I left some comments. Also, it needs unit tests in principle.
BTW, as I commented earlier, AsyncRawSocketSender creates a thread for each invoking emit()
method and I'm concerned about the performance.
Thanks for your review! I'll try to resolve issues which are pointed out.
I fixed some test failures at https://github.com/fluent/fluent-logger-java/commit/969b88d0d1ed9a5aa27e92ccc72621d524c76cdf.
Could you try git rebase master
to it?
Rebased!
@cosmo0920 Thanks! I left some comments on the diff. Especially, https://github.com/fluent/fluent-logger-java/pull/49/files#r61833474 is an issue, I think.
BTW, will you actually use AsyncRawSocketSender? If so, what do you think about creating an EmitRunnable for each emit()
call in terms of performance. If it's just experimental, why don't you add a comment like this on the class? This feature is highly experimental
BTW, will you actually use AsyncRawSocketSender?
No, I won't. It's just an experimental.
why don't you add a comment like this on the class?
This feature is highly experimental
I've added this one in javadoc comment.
@cosmo0920 Sorry for late reply again. Could you check this comment? https://github.com/fluent/fluent-logger-java/pull/49/commits/1bf11d7bdbbbec13c84eea384acc3a2bf8488e3e#r65201214