> On 4. Mar 2019, at 16:12, Marcus Denker wrote:
>
Thanks for the help!
[ToC]
I try to keep it brief so please tell me when to elaborate more.
(1) Handling of default values.
(2) Fast lazy initialization of OrderedCollection for repeated fields
(3) Installation of selectors based on the
> On 5. Mar 2019, at 19:06, HenrikNergaard5 wrote:
>
> Hi Holger,
>
>> My plan of action is to start with a protobuf compiler/model and then look
>> into binding the gRPC C implementation to Pharo.
>
> I have an almost complete parser and compiler (class generation)
> implementation of
Hi Holger,
> My plan of action is to start with a protobuf compiler/model and then look
> into binding the gRPC C implementation to Pharo.
I have an almost complete parser and compiler (class generation)
implementation of protobuf in Pharo around somewhere...
I cant quite remember the state of
Hello!
Nice, I will have a look.
I am interested to see how class layouts / slots can be used here.
(but it might take some days to find time…)
Marcus
> On 26 Feb 2019, at 07:54, Holger Freyther wrote:
>
> Hi,
>
> from my point of view the pillars of future services are Google
Hi,
from my point of view the pillars of future services are Google protobuf[1] and
gRPC. Protobuf can be used for configuration files[2], tracing/logging[3] and
storage[4]. gRPC is built on top-of HTTP2 and is using the protobuf IDL and
marshaling. Many projects (etcd, envoy, Google Cloud,
