Skip to Content.
Sympa Menu

shibboleth-dev - RE: More defined custom extensions mechanism

Subject: Shibboleth Developers

List archive

RE: More defined custom extensions mechanism


Chronological Thread 
  • From: "Scott Cantor" <>
  • To: "'Ian Young'" <>
  • Cc: "'Shibboleth Developers'" <>
  • Subject: RE: More defined custom extensions mechanism
  • Date: Sat, 9 Jul 2005 13:28:23 -0400
  • Organization: The Ohio State University

> Was there a reason that the -targetconfig specifies it as "a sequence of
> (any number of Library elements) followed by (any number of anything
> else)" rather than "a sequence of any number of (a choice between a
> Library element and anything else)" ? Or in other words, is there any
> reason why the Library elements all needed to come at the start of the
> Extensions?

Convention is to put known content first. XML is not easy to navigate and
knowing the position of content you care about is most of the work. The more
predictability the better.

Of course that only works when validating. If we turn that off, the code has
no idea where anything is, and I suspect we'll be chasing bugs for years.

-- Scott




Archive powered by MHonArc 2.6.16.

Top of Page