On Tue, 8 Jan 2008, Darren J Moffat wrote:
> Which is why this is a Volatile interface - so that when the future case comes
> along to do this more generically if it needs to it can move the mapping
> modules provided by this case.
>
> I don't see anything in this case that stops the project team providing a
> generic cert mapping functionality later, even based on the modules that this
> case provides.
ok, good point. I didn't realize that mapper pathnames were
volatile, I mistakenly read that as "modules", not "module". Thanks, J.
--
Jan Pechanec
