From: Daniil Baturin <daniil@baturin.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Protobuf for ocaml
Date: Sun, 11 Feb 2018 22:00:06 +0700 [thread overview]
Message-ID: <e6a8d003-a954-1bac-5d99-afb1b99c8517@baturin.org> (raw)
In-Reply-To: <trinity-e56f3419-e31e-4f0a-9cbb-8a034a09c17f-1518358511441@3c-app-webde-bap56>
[-- Attachment #1.1: Type: text/plain, Size: 889 bytes --]
Hi Florian,
It took me some time to get over the fact that Protobuf is just a
payload encoding protocol: no less, but no more. You can think of it as
OSI layer 6 (presentation).
Everything else, including reliable (or unreliable) delivery (layer 4),
message routing (layer 3), or even the wire protocol are separate concerns.
You may want to look into existing message transport solutions such as
ZMQ if the situation is more complicated than point to point stateless
communication.
On 02/11/2018 09:15 PM, picflo_2@web.de wrote:
> Hi,
>
> thanks for all the answers, I will look deeper into ocaml-protoc.
>
> As a kind of follow-up question. Do you add some kind of unique
> identifier to every message to allow resending the message in case
> some service goes down?
>
> Thanks again for the help here I highly appreciate it,
> Florian
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next prev parent reply other threads:[~2018-02-11 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 18:05 picflo_2
2018-02-10 18:56 ` Kenneth Adam Miller
2018-02-11 0:43 ` Louis Roché
2018-02-11 1:09 ` Kenneth Adam Miller
2018-02-11 2:15 ` Maxime Ransan
2018-02-11 14:15 ` Aw: " picflo_2
2018-02-11 15:00 ` Daniil Baturin [this message]
2018-02-11 15:01 ` Maxime Ransan
2018-02-11 15:14 ` Aw: " picflo_2
2018-02-10 18:59 ` Daniil Baturin
2018-02-11 12:16 ` SP
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6a8d003-a954-1bac-5d99-afb1b99c8517@baturin.org \
--to=daniil@baturin.org \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).