Check Snap, they use gRPC to register plugins:
https://github.com/intelsdi-x/snap/blob/master/control/plugin/client/grpc.go
Best,
Alejandro
From: golang-nuts@googlegroups.com on behalf of
sanka...@gmail.com
Sent: Saturday, January 28, 2017 10:33:26 PM
To: golan
But is it possible to finalize a discussion about finalizers?
John
John Souvestre - New Orleans LA
From: Michael Jones [mailto:michael.jo...@gmail.com]
Sent: 2017 January 29, Sun 20:38
To: Val
Cc: golang-nuts; j...@souvestre.com
Subject: Re: [go-nuts] Re: I know finalizers are not pro
On Windows I've always had to set GOBIN when doing "go install". If not I get
an error message: "go install: no install location for .go files listed on
command line (GOBIN not set)". Shouldn't the default GOPATH\bin directory be
used in this case? That's what I believe I see described in all th
"endeavor to"
"anticipate"
"allow for"
"prepare for"
"encourage"
"facilitate"
...good
"ensure" / "force" / "guarantee" (not in your control)
"reclaim" / "recycle" / "release" (too absolute)
...bad
On Sun, Jan 29, 2017 at 4:51 PM, Val wrote:
> Hello Jesper
> if I understand this thread cor
Hello Jesper
if I understand this thread correctly, "make sure" should be rephrased by
"make extra efforts for ...".
Sorry for nitpicking (not trying to look pedantic or arrogant)
Val
On Sunday, January 29, 2017 at 4:28:09 PM UTC+1, Jesper Louis Andersen
wrote:
>
>
> you'd like to eventually
Hi,
some major updates here,
1. much less ugly //go:generate comments.
Rather than passing arguments to template-compiler,
you declare a configuration variable into your code,
template-compiler will locate and export it via the ast (amazing what we
can do with it)
So now it look likes this,
//
Hi,
maybe, should you load the program via the loader,
it helps *a lot* to deal with types relationships and many other things.
https://github.com/golang/example/tree/master/gotypes
https://godoc.org/golang.org/x/tools/go/loader
Now to understand the tree and understand it, I found this was usef
Hi
I am looking for any FOSS projects (or a tutorial) which covers the
following end-to-end aspects of gRPC services (implemented via golang)
1) Authentication and Session management
2) Deployment of these gRPC services via kubernetes locally as well as in
production
3) Testing practices for th
Current doc says
ReadFrom reads data from r until EOF or error. The return value n is the
> number of bytes read. Any error except io.EOF encountered during the read
> is also returned.
WriteTo writes data to w until there's no more data to write or when an
> error occurs. The return value n
On Sat, Jan 28, 2017 at 10:22 PM John Souvestre wrote:
> > If finalizers were indeed totally useless, it would obviously be totally
> useless to implement support for them.
>
> If someone described a few cases where finalizers were useful perhaps it
> would help understand them.
>
>
The common c
Sweet. Thanks gents. Still fairly new to Golang.
I followed Matt's example and was able to get it working.
On Sun, Jan 22, 2017 at 6:52 PM, Matt Harden wrote:
> Note that you can't use lowercase struct field names with encoding/json
> anyway, because fields must be exported for encoding/json to
How do you want the feedback?
To sum up me feelings: lgtm
;-)
On Sat, Jan 28, 2017 at 4:05 AM Matt Silverlock wrote:
> gorilla/sessions has been around for a while, and with request.Context()
> back in Go 1.7, there's an unavoidable need to make breaking changes to the
> library. While we're a
12 matches
Mail list logo
