I could possible offer some assistance if the effort would be along the lines
of porting log4j2 to .NET. As I mentioned, I had suggested this on the log4net
mailing list and while they were not totally against it there seemed some
concern, rightly so, on the overall effort and possibly not
ks across Java and .NET.
> >
> >
> > Thanks,
> >
> > Nick
> >
> >
> > From: Ralph Goers
> > Sent: Tuesday, October 18, 2016 8:08 PM
> > To: Log4J Users List
> > Subject: Re: porting log4j2 to .NET
>
>
>
> Thanks,
>
> Nick
>
>
> From: Ralph Goers
> Sent: Tuesday, October 18, 2016 8:08 PM
> To: Log4J Users List
> Subject: Re: porting log4j2 to .NET
>
> I feel lost because I don’t understand the concept of a code base that
> w
,
Nick
From: Nicholas Duane
Sent: Tuesday, October 18, 2016 9:36 PM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
But I'm not suggesting a code base that will run everywhere. As I said, I'm
not talking about a single source code base.
d in it going off
in its own direction as I see a big benefit in having similar logging
frameworks across Java and .NET.
Thanks,
Nick
From: Ralph Goers
Sent: Tuesday, October 18, 2016 8:08 PM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
I feel lost b
with my questions as I try to
> work though the issues I have with our implementation.
>
>
> Thanks,
>
> Nick
>
>
> From: Ralph Goers <mailto:ralph.go...@dslextreme.com>>
> Sent: Tuesday, October 18, 2016 4:25 PM
> To: Log
difficult.
By the way, thanks to everyone for putting up with my questions as I try to
work though the issues I have with our implementation.
Thanks,
Nick
From: Ralph Goers
Sent: Tuesday, October 18, 2016 4:25 PM
To: Log4J Users List
Subject: Re: porting log4
nfigured
> programmatically
>
>
> I'm sure there's some stuff I'm missing. Still not sure why most of the
> design for this has to know what runtime/language it's targeting.
>
>
> Thanks,
>
> Nick
>
> _________________
ctober 18, 2016 12:22 PM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
Really, the only portable-ish way to make a common framework would be to
write them in C or Rust or something and make glue code for every runtime
out there. JVM users tend to prefer Java-native libraries over
JNI/JNA
r.
> > > >
> > > >
> > > > Also not sure about the OOP thing. As far as I can tell, OOP is
> just a
> > > > convenience thing, syntactic sugar. I believe you can do the same
> in a
> > > > procedural language.
> > > >
esigned OS/runtime
> > agnostic
> > > and without having to design to a lowest common denominator.
> > >
> > >
> > > Also not sure about the OOP thing. As far as I can tell, OOP is just a
> > > convenience thing, syntactic sugar. I beli
. I believe you can do the same in a
> > procedural language.
> >
> >
> > Thanks,
> >
> > Nick
> >
> >
> > From: Matt Sicker
> > Sent: Tuesday, October 18, 2016 10:37 AM
> > To: Log4J Users List
>
icker
> Sent: Tuesday, October 18, 2016 10:37 AM
> To: Log4J Users List
> Subject: Re: porting log4j2 to .NET
>
> Every programming language has its own idioms, and that even goes for all
> the various JVM languages as demonstrated by the log4j-scala API. Unless
> you mean mor
actic sugar. I believe you can do the same in a
procedural language.
Thanks,
Nick
From: Matt Sicker
Sent: Tuesday, October 18, 2016 10:37 AM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
Every programming language has its own idioms, and that even goe
ferent. Maybe there's even a feature that
> one implementation has that others don't just because there is no way, or
> no easy enough way to implement.
>
>
> Thanks,
>
> Nick
>
> ____________________
> From: Mikael Ståldal
> Sent: Tuesday
ffer is full it compresses it and sends it via http to
one of our endpoints.
Thanks,
Nick
From: Mikael Ståldal
Sent: Tuesday, October 18, 2016 10:06 AM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
...or a standardized non-binary format (like GELF, J
___
From: Mikael Ståldal
Sent: Tuesday, October 18, 2016 10:04 AM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
Maybe I am nitpicking, but Log4j is also (mostly) agnostic to what language
you run on the JVM (Java, Scala, Groovy, Clojure, etc).
I guess it would be nice t
g to pick a logging
> framework
> > to use and I find a popular one which is capable and runs similarly
> across
> > the OS's and languages then that's a big plus in my mind.
> >
> >
> > Thanks,
> >
> > Nick
> >
> > _________
nguages then that's a big plus in my mind.
>
>
> Thanks,
>
> Nick
>
>
> From: Mikael Ståldal
> Sent: Tuesday, October 18, 2016 2:52 AM
> To: Log4J Users List
> Subject: Re: porting log4j2 to .NET
>
> Just to make things c
x27;s a big plus in my mind.
>>
>>
>> Thanks,
>>
>> Nick
>>
>> ____________
>> From: Mikael Ståldal
>> Sent: Tuesday, October 18, 2016 2:52 AM
>> To: Log4J Users List
>> Subject: Re: porting log4j2 to .NET
>&
Nick
>
>
> From: Mikael Ståldal
> Sent: Tuesday, October 18, 2016 2:52 AM
> To: Log4J Users List
> Subject: Re: porting log4j2 to .NET
>
> Just to make things clear, Log4j is a logging framework for the JVM
> platform, and it is agnostic to the
Mikael Ståldal
Sent: Tuesday, October 18, 2016 2:52 AM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
Just to make things clear, Log4j is a logging framework for the JVM
platform, and it is agnostic to the underlying OS. It it well tested on (at
least) both Linux and Windows.
On Tue, Oct
I have already
> had some email exchanges with the log4net mailing list regarding porting
> log4j2 to .NET. My suggestion was that the apache logging framework be a
> single architecture design which is platform agnostic and then teams which
> port to the different platforms. It seem
we double your estimate, 3 people taking
4 months? Doesn't sound too bad.
Thanks,
Nick
From: Gary Gregory
Sent: Monday, October 17, 2016 8:54 PM
To: Log4J Users List
Subject: Re: porting log4j2 to .NET
Random guesstimate for a complete port, including tests
ave already
> had some email exchanges with the log4net mailing list regarding porting
> log4j2 to .NET. My suggestion was that the apache logging framework be a
> single architecture design which is platform agnostic and then teams which
> port to the different platforms. It seems log4ne
Figured I would send this question out to the log4j side. I have already had
some email exchanges with the log4net mailing list regarding porting log4j2 to
.NET. My suggestion was that the apache logging framework be a single
architecture design which is platform agnostic and then teams which
26 matches
Mail list logo
