LocalDynamicMetadataProvider at the SP

[Rod Widdowson]

As Nate says only the Directory and XML metadata providers can driver a discovery feed (as can be determined by the lack of
"discoveryFeed" attribute for the other types.)

It's not immediately obvious to me what a discovery feed would mean:

	"Provide the complete list of all the entities I can speak to, but do so without loading or otherwise touching any
information for these entities (including their names) until such time as I need them".  

The only way of squaring that circle is to glom all the data into one file or directory and loading it up, which brings us back to
where we started with huge reload times and loads of memory.

Think of it like DNS.  Back when we lived with /etc/hosts files only it was reasonable to find out about every computer in your
universe.  These days it is less so.  

I don't doubt the utility of such a beast, I just doubt the feasibility - without an outside agency (and to push the DNS analogy
beyond anything reasonable, this was when AltaVista and it's descendants came in).  

In my observation interest in IdP Discovery cycles with a frequency of about 3 or 4 years, so any time now someone is going to spot
it and do it again....  

In the mean time as Nate also said I think that the MDQ create JSON, but the download time is non negligible.   The next solution
might involved AJAX from a centralized point of failure, I mean server.

Discovery is hard.  I have the wounds.

What are you trying to achieve?