Dan wrote:
> At the moment I'm thinking of the load path as an array of subs that 
> get passed in the file being looked for and return... something. I'm 
> not sure what, though.

Don't reinvent the wheel here.  Obviously what should be return is an URI.
If we start off only supporting "file://..." okay, but eventually we
should support full over-the-net URI's (http:, https:, ftp:, etc.).


--
Mark Biggar
[EMAIL PROTECTED]

Reply via email to