You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to support writing to rolling files - regardless of the writer being used.
I suggest refactoring the logic from being a separate writer into a shared abstraction by all writers. However I only skimmed the codebase and I am not sure if this would risk introducing a performance overhead.
On a more personal/customer side note, I am also considering the ROI on switching to something like kotlin-logging + Logback vs. implementing this in Tinylog. I personally prefer Tinylog, so I am looking for your thoughts on this @pmwmedia .
The text was updated successfully, but these errors were encountered:
It would be nice to support writing to rolling files - regardless of the writer being used.
I suggest refactoring the logic from being a separate writer into a shared abstraction by all writers. However I only skimmed the codebase and I am not sure if this would risk introducing a performance overhead.
On a more personal/customer side note, I am also considering the ROI on switching to something like kotlin-logging + Logback vs. implementing this in Tinylog. I personally prefer Tinylog, so I am looking for your thoughts on this @pmwmedia .
The text was updated successfully, but these errors were encountered: