Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@edgent.apache.org
MIME-Version: 1.0
From: =?UTF-8?Q?Otis_Gospodneti=C4=87?= <otis.gospodnetic@gmail.com>
Date: Fri, 29 Dec 2017 16:41:23 -0500
Message-ID: <CANNBgPKHnSuuKGj7FqziPTKEvsoWgXiJ+f4Zg2qPR8VPR+yHKw@mail.gmail.com>
Subject: Buffering on the edge (network issues)
To: dev@edgent.apache.org
Content-Type: multipart/alternative; boundary="94eb2c190cba7530210561817e2d"
archived-at: Fri, 29 Dec 2017 21:41:34 -0000

--94eb2c190cba7530210561817e2d
Content-Type: text/plain; charset="UTF-8"

Hi,

I tried looking through the API and examples to see if there is Edgent has
any built-in buffering capabilities for when the sink cannot be reached for
whatever reason.  I couldn't find anything like that. Is that something
that one would have to write for each (new or custom) connector or is that
a part of the framework and I just missed it?

If I missed it, how is buffering implemented?
In-memory or on persistent media or some hybrid?
Can one define the max buffer capacity in terms of either number of items
or bytes?
If so, are the oldest items in the buffer dropped when the max capacity (or
their age) is reached?

Thanks,
Otis
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/

--94eb2c190cba7530210561817e2d--