Re: RSocket Followup (post TOC meeting)
|
Robert Roeser <robert@...>
Hi Justin,
From the go people I talked with we can use go channels for request stream and request channel. For request / response and fire forget people could be a use a go routine. I am not a go expert but understanding is that you could use
buffered channels with the RSocket request n semantics effectively.
I was told the interfaces could be idiomatic go.
Thanks,
Robert
Get Outlook for iOS
From: Justin Cormack <justin.cormack@...>
Sent: Wednesday, August 8, 2018 3:27:23 PM To: Chris Aniszczyk Cc: CNCF TOC; Robert Roeser; Ben Hale Subject: Re: [cncf-toc] RSocket Followup (post TOC meeting) The Go question came up in the call, which is interesting as much of the CNCF ecosystem is currently
Go based, although diversifying. Go is unusual in not supporting async interfaces really, prefering
to do explicit sync threading. The rsocket protocol is just a wire protocol, but I am curious if anyone
has looked at what the programming interface for Go might look like and whether maintaining this
might be an issue.
On Tue, Aug 7, 2018 at 5:04 PM, Chris Aniszczyk
<caniszczyk@...> wrote:
|
|
|