I appears to me that your question is not so much as to how to handle the conversion but how to present your product or service to your users. In this sense, I think you need to really ask yourself, "What is the goal of my file conversion service?"

First, if you are not going to be providing this service for classified documentation then you don't really need to worry about what the end user thinks the security of their files are. Like you stated, we all know that transmission over http is insecure. So, maybe you need to look at developing a terms of service agreement that will release you of any liabilites including copyright and patent rights that the end user may claim to have for using your service. In this sense then you can worry about the disk space problems and clean up yourself that a simple cron job or perl script can solve.

However, if you are going to offer a corporate level solution then a free iDisk idea is perhaps the best idea. But dont try to make your users feel safe. Use the appropiate security measures such as secure http and ssl.

This decision lies in your hands. "Keep it simple. Enlightenment will come to you as long as your motivation is true."

Good Hunting,
kha0z

In reply to Re: Browser-based file uploads and deletions for a by kha0z
in thread Browser-based file uploads and deletions for a by hacker

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.