+1 from me, too.
i'm wondering though, if there could be a more elegant solution to the
SSL issue. i.e rather than requiring two registry entries with their
own https-conditions, why not make that decision at render time i.e.
in the template? (i.e. Products/ResourceRegistries/www/
Right. I do mention that in the PLIP. I had considered an option to allow
that cleverness through an option to follow the SSL-ness of the current
request, always be SSL, or never be SSL on a given resource. The major
counter point to this is Google Analytics which has two different domains
for its
