shibboleth-dev - Re: More defined custom extensions mechanism

Subject: Shibboleth Developers

List archive

Re: More defined custom extensions mechanism

From: Tom Scavo <>
To: Walter Hoehn <>
Cc: Chad La Joie <>, Shibboleth Developers <>
Subject: Re: More defined custom extensions mechanism
Date: Wed, 6 Jul 2005 17:38:52 -0400
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X5sV6d+RRhk0UpFmyNfTcIl9ii8j1DWz/6dvxBP92MosjlZ4rZfuI7lxDlHzT4RNPt/DXlxmaL5DihcoA3DgnUINZDZ7924Bv/2BCBisbmOZ15WfpSb8j4PSPCrWdJ+w1xgMSnCEDToqmTl5hsppLhmwkZfrjqDOKtWhBPh0t34=

On 7/6/05, Walter Hoehn
<>
wrote:
> On Jul 6, 2005, at 4:30 PM, Tom Scavo wrote:
> >
> > Good point. So I'm back to my original question: Does the plugin
> > directly read the files in $IDP_HOME$? Is that the recommended
> > approach?
>
> That is what I'm recommending, yes. I think it simplifies things
> quite a bit for you.

Yes, it does, thanks.

> If you want it to be harder for the build
> script to overwrite the stuff in this directory, we can certainly
> work on that.

What are your thoughts on this issue, Walter?

Thanks,
Tom

Re: More defined custom extensions mechanism, (continued)

List archive

Re: More defined custom extensions mechanism