Shibboleth Developers

[Tom Scavo <>]

On 4/29/05, Walter Hoehn 
<>
 wrote:
> 
> My opinion is that an internal API in shibboleth reaches the third
> category only when we have a discussion like the one we are having now
> where somebody says "hey, stability in this particular area is
> important to me".  So, we can try to work with folks in this regard,
> but they shouldn't be making assumptions without speaking up.

Oh, we had every intention of letting you know what our "touch points"
were, I just didn't realize the topic would come up so early. ;-) 
Really though, an API for building custom plugins should be considered
frozen or at least subject to a phased obsolescence plan of some kind.
 An informational post to shib-dev is not sufficient...you need to
communicate ahead of time what portions of your API you consider
public.  Then the discussion in shib-dev centers around what
interfaces belong to that public API.

What's needed is a developer's guide.  Not just "how to" stuff (which
is important) but a published list of interfaces you consider public. 
Everything else is "at your own risk".

Tom