On Wed, 25 Mar 2020 at 23:11, Peter Silva wrote:
> Most Sarrracenia stuff is tied to AMQP, but next-gen messages are called
> v03 (version 3) they use a JSON payload
> for all the information, and that makes it somewhat protocol independent.
> There is also a 500 line MQTT demo
> that implements
Most Sarrracenia stuff is tied to AMQP, but next-gen messages are called
v03 (version 3) they use a JSON payload
for all the information, and that makes it somewhat protocol independent.
There is also a 500 line MQTT demo
that implements a file replication network, using the same JSON messages,
and
I was looking into the email approach more and maybe I found a few
improvements:
- each communicating agent has an exim instance
- there are a few dns servers that replicate their configuration between
each other (to provide redundancy)
- these servers store subscriptions of the agents for each to
>
>
> I work in telecom for meteorology, and we ended up with a general method
> for file copying (catchphrase: rsync on steroids*.) ( *every catchphrase is
> a distortion, no dis to rsync, but in certain cases we do work much faster,
> it just communicates the idea.) Sarracenia (
> https://github
On Wed, 25 Mar 2020 at 01:00, clime wrote:
>
> On Tue, 24 Mar 2020 at 22:45, Nicolas Dandrimont wrote:
> >
> > On Tue, Mar 24, 2020, at 21:51, clime wrote:
> > > On Tue, 24 Mar 2020 at 20:40, Nicolas Dandrimont wrote:
> > > >
> > > > Hi!
> > > >
> > > > On Sun, Mar 22, 2020, at 13:06, clime wrot
On Tue, 24 Mar 2020 at 22:45, Nicolas Dandrimont wrote:
>
> On Tue, Mar 24, 2020, at 21:51, clime wrote:
> > On Tue, 24 Mar 2020 at 20:40, Nicolas Dandrimont wrote:
> > >
> > > Hi!
> > >
> > > On Sun, Mar 22, 2020, at 13:06, clime wrote:
> > > > Hello!
> > > >
> > > > Ad. https://lists.debian.org
On Tue, Mar 24, 2020, at 21:51, clime wrote:
> On Tue, 24 Mar 2020 at 20:40, Nicolas Dandrimont wrote:
> >
> > Hi!
> >
> > On Sun, Mar 22, 2020, at 13:06, clime wrote:
> > > Hello!
> > >
> > > Ad. https://lists.debian.org/debian-devel/2016/07/msg00377.html -
> > > fedmsg usage in Debian.
> > >
> >
Hi Clime,
On 24-03-2020 21:51, clime wrote:
> So do you have the opposite? I do some clicking action somewhere and
> it will send an email to a certain mailing list to inform human
> beings? Or let's not just clicking but e.g. `git push` (something that
> you can still do from command line).
>
>
On Tue, 24 Mar 2020 at 20:40, Nicolas Dandrimont wrote:
>
> Hi!
>
> On Sun, Mar 22, 2020, at 13:06, clime wrote:
> > Hello!
> >
> > Ad. https://lists.debian.org/debian-devel/2016/07/msg00377.html -
> > fedmsg usage in Debian.
> >
> > There is a note: "it seems that people actually like parsing ema
Hi!
On Sun, Mar 22, 2020, at 13:06, clime wrote:
> Hello!
>
> Ad. https://lists.debian.org/debian-devel/2016/07/msg00377.html -
> fedmsg usage in Debian.
>
> There is a note: "it seems that people actually like parsing emails"
This was just a way to say that fedmsg never got much of a user base
MQTT is the best thing going for interop purposes.
On Tue, Mar 24, 2020 at 1:20 PM Jeremy Stanley wrote:
> On 2020-03-24 13:09:35 -0400 (-0400), Peter Silva wrote:
> [...]
> > We could talk about the merits of various protocols (I see fedmsg
> > uses ZeroMQ) but that is a deep rabbit hole... to
On 2020-03-24 13:09:35 -0400 (-0400), Peter Silva wrote:
[...]
> We could talk about the merits of various protocols (I see fedmsg
> uses ZeroMQ) but that is a deep rabbit hole... to me, fedmsg looks
> like it is making a ZeroMQ version of a broker (which is a bit
> ironic given the original point
hi, totally different take on this...
We could talk about the merits of various protocols (I see fedmsg uses
ZeroMQ) but that is a
deep rabbit hole... to me, fedmsg looks like it is making a ZeroMQ version
of a broker (which is a bit ironic given the original point of that
protocol) trying to buil
The email backend might be quite a heavy-weight idea ... although I
think it would do the job if properly setup and _very_ reliably. I was
thinking about something similar to google pub/sub.
Another approach how to add reliability to the current fedmsg would be
to add an optional sqlite persistenc
Hello!
Ad. https://lists.debian.org/debian-devel/2016/07/msg00377.html -
fedmsg usage in Debian.
There is a note: "it seems that people actually like parsing emails"
What about adding email backend to fedmsg then. Wouldn't it be an
interesting idea? It could basically rely on postfix for sending
15 matches
Mail list logo
