From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a02:5693:: with SMTP id u19mr519312jad.5.1551385118598; Thu, 28 Feb 2019 12:18:38 -0800 (PST) X-Received: by 2002:aca:af85:: with SMTP id y127mr1020383oie.83.1551385118220; Thu, 28 Feb 2019 12:18:38 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!y42no349ita.0!news-out.google.com!d79ni18itc.0!nntp.google.com!y22no953ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 28 Feb 2019 12:18:37 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2804:14c:4c1:939b:2ced:f5af:9283:9555; posting-account=wgmHdgoAAAA-F7JItPEZjeXqFc0KdzEQ NNTP-Posting-Host: 2804:14c:4c1:939b:2ced:f5af:9283:9555 References: <42ec3738-180f-468b-9a4b-1763a14bad40@googlegroups.com> <4dfbb6c5-8955-4d3a-b886-4c09427d6d1e@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <336a6d23-3586-4593-96e5-514508d10c03@googlegroups.com> Subject: Re: ? Are there LDPC error code lib in Ada ? thanks. From: Daniel Norte Moraes Injection-Date: Thu, 28 Feb 2019 20:18:38 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:55721 Date: 2019-02-28T12:18:37-08:00 List-Id: Em s=C3=A1bado, 23 de fevereiro de 2019 04:49:41 UTC-3, Dmitry A. Kazakov = escreveu: > On 2019-02-22 23:22, Daniel Norte Moraes wrote: >=20 > > Main objective is "forward error recover" e.g: > > 1) try automatic recover data in engine of distributed database befo= re > > need to ask for retransmission data from nodes >=20 > If transmission errors occur they do not manifest themselves as=20 > corrupted data, because the transports already correct these. They do as= =20 > undelivered data, dropped connections, missed deadlines, lost integrity e= tc. >=20 > > 2) and auto-recover for data received. >=20 > There is no recovery from non-delivery. You can improve situation using= =20 > redundant nodes and some sort of consensus in the scenario when some=20 > nodes might go offline. Error correcting codes is no help at this level= =20 > of abstraction (application's OSI). >=20 > --=20 > Regards, > Dmitry A. Kazakov > http://www.dmitry-kazakov.de Hi! :-) Just to heal my doubt: =20 Is Better double the data and verify crc and if one is corrupted (and the= other is ok) substitute the corrupted with the good one ? It is ok for me, too. I remmenber CouchDb use this aproach. this will sim= plifly my code, too. :-) []'s Grateful, Dani. :-)=20