Server: use proper logging utility about horizon

[deontologician]

Sounds good to me. I intend to remove all of the protocol noise eventually, I just needed that when the server and client really weren't talking the same language.

Before you do it though, I want to merge my refactor branch to master, it rewrites pretty much every line in the client so it'll be a bad merge conflict

[coffeemug]

I think Marshall was talking about server logging, not client logging (unless I'm mistaken), so there should be no conflicts.

[deontologician]

Oh whoops

On Thu, Nov 5, 2015, 13:07 Slava Akhmechet [email protected] wrote:

I think Marshall was talking about server logging, not client logging
(unless I'm mistaken), so there should be no conflicts.

—
Reply to this email directly or view it on GitHub
#17 (comment).

[Tryneus]

@marshall007 - I was actually about to integrate a logging system - I'm working on tests right now, and the server is really spammy and annoying - I hope you don't mind if I take care of this right away. For the record, I don't know much about the node ecosystem, so I'll try out winston.

[marshall007]

@Tryneus sure, no problem!

[Tryneus]

@marshall007, alright, just pushed my latest changes in eee4da7 - the server now exports a logger field, which is a winston object. Most of the old log statements are now at the debug level. Thanks for bringing this up!