[Avalon.NET] Framework Interfaces

[Berin Loritsch]

Ok, I think I am done with updating the interfaces for Avalon.NET framework.
The assumption here is that we will use the System.IDisposable interface instead
of requiring developers to use one in the Apache.AvalonFramework namespace.
Please present your comments so I can incorporate them.

Also, as to preferred namespace (not critical, but better to get it out of the
way now).  We have a few options, please mark your preference with a +1 below:
Apache.Avalon  -> This would be reserved ONLY for the framework.  All container
                  code is elsewhere
Apache.AvalonFramework  -> More clear.  It is what we currently have.

Apache.Avalon.Framework -> Again more clear, but now we have three layers of
                           namespaces.
The last alternative is to simply remove the "Apache" name from the namespace,
having that implied by the Apache Software License included in each file.  It
might be confused with Microsoft's nebulous "Avalon" project that people have
hinted at.  Alternative (again) is to fuse the Apache and Avalon names into
ApacheAvalon.**
I honestly don't have a preference one way or the other.  I just prefer to
maintain consistency in namespace style accross all our Avalon.NET projects.
Also, we should probably refrain from the *.NET reference as that is truly
a Microsoft trademark thing, although Avalon# would be ok.
--

"They that give up essential liberty to obtain a little temporary safety
 deserve neither liberty nor safety."
                - Benjamin Franklin


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]