*[My answers are inline.]*
On Thu, Jul 1, 2021 at 11:48 PM Raman Gupta wrote:
>
> https://issues.apache.org/jira/browse/LOG4J2-3116
> https://github.com/apache/logging-log4j2/pull/543
>
Thanks! I will check these out momentarily.
> One administrative note -- as I am a committer (although thus
When testing the passage of time, you can always try mocking the clock
itself to simulate things like that. In some cases, use of count down
latches or cyclic barriers can coordinate the various async actions rather
than relying on clocks. Once you start testing and modeling these things
like that,
Hm, I might be missing some context. I thought this thread about releasing
a component, then someone brings up message queuing ("pub/sub"), now a web
browser? I'm missing something for sure!
Gary
On Sun, Jul 4, 2021, 14:02 Ralph Goers wrote:
> Umm, how would you use JMS from the browser? Mosqui
Umm, how would you use JMS from the browser? Mosquitto looks like it might have
more promise since it supports TLS and OAuth, but from a quick glance it
appears it
is its own protocol, not something that sits on top of HTTP, so it might be
more challenging
to use through a public firewall.
To
We already have support for JMS, this is a simple as possible set up.
Gary
On Sun, Jul 4, 2021, 11:49 Dominik Psenner wrote:
> Hi,
>
> I would rather advise to not reinvent the wheel of tcp communication but
> implement some simplistic mqtt appender that transports log events as json
> serializ
Hi,
I would rather advise to not reinvent the wheel of tcp communication but
implement some simplistic mqtt appender that transports log events as json
serialized messages.
In combination with a broker like mosquitto it provides secure
communication, temporary peristent storage and many more adva
