[OWASP-ESAPI] Question about .NET ESAPI namespaces
dan at denimgroup.com
Mon Aug 31 17:06:44 EDT 2009
I would think it would be good to have the package structures mirror one another if possible for folks who switch back and forth between the .NET and Java versions. For example, our folks use both ESAPI Java and ESAPI.NET, depending on the project they are working on. Keeping the packaging and APIs as similar as is reasonable would be of benefit to my guys.
From: owasp-esapi-bounces at lists.owasp.org on behalf of Alex Smolen
Sent: Mon 8/31/2009 3:57 PM
To: Boberski, Michael [USA]
Subject: Re: [OWASP-ESAPI] Question about .NET ESAPI namespaces
I didn't move the reference implementation to its own namespace. I
didn't exactly mirror the ESAPI Java implementation in other ways as
well, but it's pretty close. The reason for this is that the .NET
version mirrored the older Java version, and I never switched over to
the new structure (partially because I couldn't see the reasoning
behind the move)
I can't see anything wrong with the namespaces as is, other than they
don't exactly match the Java version. Do you see something about the
current .NET structure that will impede usage, or is it simply a
On Aug 31, 2009, at 12:51 PM, Boberski, Michael [USA] wrote:
> Hi, quick question about the current .NET version of ESAPI.
> What was the rationale for not mirroring the Java package structure
> in the .NET namespace structure? It's not immediately obvious to me
> that it's a ".NET thing" that caused the change.
> A follow up question would be, let us say I decided to implement my
> own .NET implementation. What should the namespace be, according to
> the current conventions? Owasp.Esapi.MikeAndCo?
> Thanks in advance, and not criticism, just trying to understand the
> Mike B.
> OWASP-ESAPI mailing list
> OWASP-ESAPI at lists.owasp.org
More information about the OWASP-ESAPI