That makes good sense - when I get a chance I'll take a look at the ASP .Net code and see if it lends itself to that approach...
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Battaglia Sent: 04 September 2007 14:28 To: Yale CAS mailing list Subject: Re: C# Client Paul, What I was thinking when I was talking about merging them is essentially this: 1. Create a service level library (i.e. what you have implemented, with anything useful from the other client) 2. Have the "web" (ASP .NET) layer utilize the service level library. This way we are only maintaining the actual validation, etc. code in one library and all other layers are basically marshalling layers to the library. It should hopefully reduce redundant code. Thoughts? -Scott On 9/3/07, Paul Hunnisett <[EMAIL PROTECTED]> wrote: The difference between this client and the existing ASP .Net client is that this is a stand alone library which can be called by any .Net application web - or non web alike. It's the difference between a jar file based client and a JSP based client. The advantage of the ASP .Net client over mine is that you can take advantage of cookies; the advantage of my client is that it can be used in contexts like SOAP web services or desktop applications where cookies and page redirects haev less or no meaning... The main motivation for writing my client is that it's only useful for ASP .Net - whereas mine can be used by any .Net application. Initially we want to use it here to log into SOAP web services which don't maintain any session data and don't use cookies. There may be some mileage in combining the two projects - although in doing so you may lose the cookie advantage of the ASP .Net client (perhaps not necessarily though...). to be honest, I'm not sure whether it would be beneficial to combine them or provide a choice given distinct advantages and disadvantages depending on your context. If I upload to the Issue tracker should I start it as a new project or add it as a component to your CAS Clients project? I'm more than happy to continue to manage and maintain it - and also take a lead in merging it with the ASP .Net client - if we decide that's the way to go... Cheers Paul ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Battaglia Sent: 31 August 2007 16:42 To: Yale CAS mailing list Subject: Re: C# Client Paul, You can initially place it in our wiki or as a JIRA issue in the our Issue Tracker (http://www.ja-sig.org/issues/). I don't know how many developers here are familiar with C# to comment on the code. Maybe you can provide us with some details. How is this different then the ASP .Net client written in C#. Is there a way to rewrite the existing one to utilize your underlying "core" libraries? Would there be interest in combining the two projects together if it makes sense? We're looking for people to volunteer to manage specific libraries under the JA-SIG banner. Thanks! -Scott On 8/31/07, Paul Hunnisett <[EMAIL PROTECTED]> wrote: No-one able to tell me where to commit this or willing to review the code? ________________________________ From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] On Behalf Of Paul Hunnisett Sent: 30 August 2007 12:30 To: Yale CAS mailing list Subject: C# Client I've built a C# client for CAS for use by .Net applications. I realise that there's already an ASP .Net client written in C#, but that assumes browser based apps. The motivation for writing mine was that we needed SOAP web services to be able to authenticate via CAS so that, where we used to pass a username and password, we now pass a ticket and they use the CAS client to authenticate. I was going to ask one of the guys round here to read through my code and review it to see if it's production quality or not but they're either on annual leave or paternity leave... So, I figured that the best thing to do was to release the client to the community, including the source code, and ask for feedback on the quality of the code. So - what's the best way of committing this? I've got both a .dll and the source code... Cheers Paul Hunnisett UWE ________________________________ This email was independently scanned for viruses by McAfee anti-virus software and none were found ________________________________ This incoming email to UWE has been independently scanned for viruses by McAfee anti-virus software and none were detected ________________________________ This email was independently scanned for viruses by McAfee anti-virus software and none were found _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia ________________________________ This incoming email to UWE has been independently scanned for viruses by McAfee anti-virus software and none were detected ________________________________ This email was independently scanned for viruses by McAfee anti-virus software and none were found _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia ________________________________ This incoming email to UWE has been independently scanned for viruses by McAfee anti-virus software and none were detected This email was independently scanned for viruses by McAfee anti-virus software and none were found
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
