Joshua C Elliott
Joshua C Elliott
Lumber is only intended to output logs. Having the logger end the program execution (e.g. with os.Exit) might not be the best behavior for all use cases. This way users...
I just ran into this issue as well. It's easy enough to parse the global ID in the config function (or convert to a global ID in the trigger I...
> We should make sure that these features "fit together" .. Agreed -- there is a lot of overlap here. For example, in a _partitioned registration_ scenario, you may want...
I was expecting `*` as well. I vote for changing it.
I personally like @ecorm's proposal here, including the change to the WELCOME message feature announcement.
The comment for `RegisterService` says that one of the requirements for a service method is "two arguments, both of exported type". What does that mean?
This is an excellent idea. I've wanted to do the same thing, but haven't had the time yet. It looks like the net/rpc [client](http://golang.org/src/net/rpc/client.go) implementation would be a great starting...
I hadn't seen that library before--I could have used it a few times in the past. It looks fairly well-tested, so I wouldn't mind depending on it. I would like...
I like the idea of a "service" interface for events. I was also thinking it would be nice to use the reflection code you added for a regular registration as...
I was thinking we would keep `RegisterService` separate, where a service is a struct with methods. Then add a reflection layer to `Register`, still registering individual functions like we do...