Expected Behavior
the library logs stuff using SLF4J and the application controls the actual output. this will allow logging stuff like logger and thread names, etc. the library uses different log levels (trace, debug, error) for different things and it's easy to filter them out, if needed. as the output is controlled by the application, no stuff like if (WebSocketImpl.DEBUG) is needed.
also, it would be nice to have a proguard rule file that would remove the logging messages from the code.
Current Behavior
the library prints its debug messages to stdout in a pretty raw form. all messages, accordingly, are of the same “level” and are inconsistent with the other messages that the application prints
Possible Solution
use SLF4J
Expected Behavior
the library logs stuff using SLF4J and the application controls the actual output. this will allow logging stuff like logger and thread names, etc. the library uses different log levels (trace, debug, error) for different things and it's easy to filter them out, if needed. as the output is controlled by the application, no stuff like
if (WebSocketImpl.DEBUG)is needed.also, it would be nice to have a proguard rule file that would remove the logging messages from the code.
Current Behavior
the library prints its debug messages to stdout in a pretty raw form. all messages, accordingly, are of the same “level” and are inconsistent with the other messages that the application prints
Possible Solution
use SLF4J