Shibboleth Developers

At 5:28 PM -0500 11/14/03, Scott Cantor wrote:
>  > For Windows - we should probably be aiming at a short-term
> >  solution being a COM component that provides the general Shib
> >  services as we're defining for Java target. At a very
> >  high-level -- we pass the COM component an HTTP session of
> >  some type (ie output stream, plus the HTTP request headers)
> >  and it comes back with the Shib target stuff.
>
> I would guess we can take the eventual interface defined for the Java
> "logical session" object and do it in COM without too much work. Java
> language interfaces and COM interfaces are fairly equivalent.
>
> >  COM then provides the most flexibility for exposing Shib
> >  behavior to Windows server applications -- IIS filters, old
> >  ASP, and .NET (aka ASPx which defaults to VB.NET for language
> >  but can also use C#). While you should try to avoid COM when
> >  programming with .NET (calling COM from .NET is a bit like
> >  calling native code from Java, though much easier), it is
> >  definitely possible.
>
> Agreed.

do we have consensus, then, around a short-term strategy of 
developing the COM component described above?

My inclination is  to do the work in two phases:

-- Phase 1 (support for htaccess-style access control, improved 
management, Improved installer package, and IIS 6 testing)  (I'll 
shortly send out a revised description of these work items)

-- Phase 2 - implement the COM component. This gives us some  time to 
agree on the actual interface....

Does this sound OK?