Il giorno mer 30 gen 2019 alle ore 18:13 Matteo Merli
ha scritto:
>
> On Wed, Jan 30, 2019 at 12:34 AM Enrico Olivelli wrote:
> > Jenkins merges the patch with current master before running tests, doesn't
> > it?
>
> I don't think this is being done by Jenkins, at least with the current
> configu
2019-01-30 19:52:39 UTC - Matteo Merli: Created <#CFTLCF52N|dev-go> for go
discussions
2019-01-30 20:52:38 UTC - Guy Feldman: Following your lead and being an
optimist I created <#CFTUA9AHK|dev-node> for node discussions
2019-01-30 20:53:01 UTC - Matteo Merli: :+1: :grinning:
I think if this feature is controlled under some flags/settings. It should
be a good tradeoff between performance concerns and
debuggability/visibility.
As what Yao said, people can choose what level of details that they would
like to see. It is similar to log4j's debug level.
Thanks,
Sijie
On T
Sure, it would be good to have that as an option.
It's just that it would need to be a completely different "operating
mode" for the proxy,
since more than the logging, is the parsing of each frame / command
that will be
"expensive".
It should be possible to do that by controlling the handlers in
Hi Matteo,
You are right, will give it a shot by using "netty".
Thanks again.
Sam
On Thursday, January 31, 2019, 6:53:03 AM PST, Matteo Merli
wrote:
Sure, it would be good to have that as an option.
It's just that it would need to be a completely different "operating
mod
Hi Sun Yao,
When you started this thread writing that the proxy is almost like a gateway.
You were correct. I think that what is wanted is for Proxies to usually be
lightweight / highly performant, and optionally become a highly resilient
Gateway.
Let’s call this new feature Gateway mode.
Re
