Greetings Monks,

In response to rinceWind's question Abstraction of FTP as a file system I did a little research and suggested using FuseFTP, which is a Perl script which allows you to mount a directory on an FTP server as a file system mount point. I think that this is a very useful program, others share my opinion. I emailed the program's author asking if he had plans to place this on CPAN. It transpires that this is not going to happen for a couple of reasons. I replied to the author asking if he had any objections to me creating a CPAN module along the lines of his program, he had none.

If you are not familiar with FUSE please take a look at the documentation. I would be interested in finding out which other protocols (webdav for example) people would be interested in having a Perl module for.

rinceWind has kindly offered me some mentoring around the whole Cpan process, and he has already offered me some help and support in a couple of other areas, for which I am very grateful. My current plan is to do some research on Cpan module authoring, more research into FUSE itself then a cycle of development and testing of the module before making it available to the public.

In an episode of Dilbert the PHB gets the order of slides mixed up in a presentation on the product development cycle: "Step 1, the name. After all if you don't know what something is called, how will do we know what to build?". The idea I have at the moment is FUSE::Remote::FTP, given that I want to leave scope for future modules to provide a Fuse interface to other protocols (FUSE::Remote::SFTP for arguments sake). I would appreciate any feedback or advice on the naming issue, and anything else I have mentioned in this post.

Thank you for your time.

References:

FUSE
FuseFTP

Update 19th August 2006 @ 00:27am changed Fuse to FUSE as per diotalevi's comment

In reply to RFC FUSE::Remote modules by marto

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.