roslibjs logging functions log to rosout.log instead of dedicated logfiles

[joshua-glazer]

Currently, logErr(), logInfo() etc result in log files generated in rosout.log. Ideally, however, each GUI webpage should generate its own logfile. My custom js log functions work by publishing to /rosout, but there may be some other hidden mechanisms in rospy behind the scenes that activate before publishing to /rosout that hold the answer.

BONUS (or future issue): For multiple operators, have some way of distinguishing logs generated from each specific operator's laptop/gui. Not sure where in the log message this would go... I've seen sometimes logs will have a "[Client 0]" show up in the messages, maybe it's related.

Some directions to investigate:

• Check out how the logging functions are implemented in rospy or roscpp. This is probably the most direct approach
• The message type used by /rosout has an entry for listing topic names. Not sure what it's used for.
• A small amount of digging has shown that the rosbridge_websocket node is responsible for all topics published by the GUI. Maybe there's something in there