I know there's a steady drumbeat of questions in this vein, but please bear with me:
Mechanically, dsLocation values are restricted to uri's with a protocol of "http" or "https" on ingest, with a special exemption for an "uploaded" protocol if the datastream is managed. In the case of managed datastreams, this restriction is enforced by java.net.URL's ability to handle the URI; in the case of external datastreams the restriction is additionally enforced by the availability of an appropriately registered implementation of org.apache.commons.httpclient.protocol.Protocol (since Fedora must be able to fetch the bytes later). 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). 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). regards, Benjamin ------------------------------------------------------------------------------ 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
