I am working on the .net cas client project with Marvin Addison. I'll check out what you have submitted and review / start building on that. I think starting with getting a working client for the 1.0 protocol sounds good.
I have been working on parsing of the SAML 1 response and will continue with that also. -----Original Message----- From: William G. Thompson, Jr. [mailto:wgt...@gmail.com] Sent: Tuesday, March 10, 2009 00:13 To: cas-dev@lists.jasig.org Subject: Re: [cas-dev] port of jasig java cas client to .net I've checked in what I've got so far in the sandbox: https://www.ja-sig.org/svn/sandbox/JasigCasClient/trunk/JasigCasClient/ I'd like to get 1.0 protocol working and then add the other protocols after that. Thoughts? Bill On Mon, Mar 9, 2009 at 9:45 PM, Marvin Addison <marvin.addi...@gmail.com> wrote: >> True, but the way accessibility modifiers work if you want to >> encapsulate "package" level functionality you need them to be in >> different assemblies (internal modifier). Accessibility and >> namespace are totally independent within an assembly, right? > > That is correct. I would argue that you could design around > accessibility limitations within a single assembly. While a faithful > port is the goal, I think we want a final product that is natural in > C#. Multiple assemblies for a product this straightforward would be > unusual. > >> If we were going to map java package visibility design to the port, >> we'd need separate assemblies. Perhaps the package/assembly >> visibility doesn't matter that much since the code base is relatively >> small. > > Agreed. Again, I believe we can design around any limitations imposed > by the language where increased accessibility may be a concern. > >> Facilitating developer understanding of the code base via >> logical organization is as important to me as easy deployment. Maybe >> this is achieved by mapping Java packages to C# namespaces in the same >> assembly arranged via folders. > > I like the folder approach for organizing the codebase. > >> Keeping alignment with the Java package structure (at least for >> namespace) should aid in the port, and help with on going maintenance >> and for those brave souls jumping from one to the other. > > I would think anyone familiar with the Java CAS client codebase would > immediately recognize that Jasig.CasClient.Validation corresponded to > org.jasig.cas.client.validation. The former is a naming convention > that is much more natural in C#. > > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@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 as: cwinf...@vt.edu 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
