Thanks for the clarification, Scott. If that is the case, should the .net port also use Commons Logging (http://bytes.com/groups/net/125095-dotnet-commons-logging)
Yes we're adding more external product dependencies - but it would be nice to keep the .NET port as mirrored as possible to the Java codebase. I personally have not used the dotnet-commons-logging, so I don't know how good/stable it is...but it might be worth looking into so that we can accomplish the same flexibility in the .NET client as we have with the java client. -Brian ________________________________ From: Scott Battaglia [scott.battag...@gmail.com] Sent: Tuesday, March 10, 2009 9:57 AM To: cas-dev@lists.jasig.org Subject: Re: [cas-dev] port of jasig java cas client to .net On Tue, Mar 10, 2009 at 9:49 AM, Pieslak, Brian <bpies...@metier.com<mailto:bpies...@metier.com>> wrote: I work in both Java & .NET, so I see log4j and log4net and I like working with relatively the same concept/framework. I personally haven't used NLog before, but I'll check it out per Michael's recommendation. For me, I think since CAS already uses log4j for Java, it would be easiest for developers to use log4net for .NET if they need to switch between languages. Just a note that both the Jasig CAS Server and Jasig CAS client v3.x utilize Commons Logging, which technically makes them logger-agnostic. The Server by default ships with Log4j but you can cut that out if you'd like. I'd say use whichever one more people are likely to have already included in their project. Not that that's necessarily a good measure (but its how we ended up with Commons Logging in the Java client ;-)). Since you're a supporting library, you want to add as little bulk as possible. -Scott -Brian ________________________________________ From: Winfrey, Catherine [cwinf...@vt.edu<mailto:cwinf...@vt.edu>] Sent: Tuesday, March 10, 2009 9:47 AM To: cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org> Subject: RE: [cas-dev] port of jasig java cas client to .net > Anyone have any thoughts, experiences, preferences for .Net loggers? log4net? If we are going to use an external product, I would also vote for log4net. However, I tend to like the idea of not adding a dependency outside of that provided by .NET unless it is needed, so I would lean toward using the system diagnostics provided by .NET. Cathy -- You are currently subscribed to cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org> as: bpies...@metier.com<mailto:bpies...@metier.com> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org> as: scott.battag...@gmail.com<mailto:scott.battag...@gmail.com> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org<mailto:cas-dev@lists.jasig.org> as: bpies...@metier.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
