Hi Benjamin, On Tue, Mar 3, 2009 at 1:17 PM, Benjamin Armintor <[email protected]> wrote: >... > I believe this means that dsLocation values of different protocols > (for example, a locally-defined "file"-like protocol) could be stuffed > into a fedora object with appropriate URLStreamHandler and Protocol > implementations to support them. My question is how much the current > restriction is a pragmatic one based on the limitations of the apache > httpclient library, or a restriction in response to other concerns (a > security concern, for example).
It's mostly pragmatic. I think it'd be a big win to just start supporting file:/// additionally (https://fedora-commons.org/jira/browse/FCREPO-453), but would also be nice to have this pluggable so people don't have to make local mods enable other protocols. > I raise the issue only because there are some non-trivial cost savings > for us in our planned fedora configuration if we work around the > restriction, but I am more wary of the approach if it violates the > spirit rather than the letter of the law (as it were). I think it's definitely in the spirit to allow content to come in via other "protocols" here. Making it pluggable would be great. Some kind of "URI content resolver" interface would seem to be in order. - Chris ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
