Skip to content

Support for parsing protocols #63

@asinghvi17

Description

@asinghvi17

It's pretty common to address files as:

protocol://path/to/file

examples of protocol being file, http[s], s3, ftp, but also things like reference (for https://fsspec.github.io/kerchunk/) or even more exotic protocols.

Should there be some form of protocol registry, and maybe an edit to the @p_str macro, which will return the correct path type if that package is loaded, and an informative error ("please load AWSS3.jl for S3 paths") if not?

For reference, https://github.com/JuliaIO/Zarr.jl already does this kind of thing, and I'd like to port quite a few of their Store objects over to a FilePathsBase like interface, since the hard work has already been mostly done.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions