Why did you even post your idea here for peer review if you are going to go defensive everytime someone points at a potential flaw in your plan?

Some very valid, and note-worthy ideas have been voiced.

Here is the only circumstance when you should use your method, in my opinion:

• Unable to ftp to web server machine, whether by name or IP.
• Unable to open ftp up on a higher order port (not good idea).
• Unable to email the file to your webserver (don't you have shell access?)
• Unable to ftp out of the web server (shell access, again?)
• NO OTHER MEANS OF TRANSFERRING FILES IS AVAILABLE

I know that I, for one, would like to know the exact environment where you believe this is warranted.

Don't get me wrong, it is a cool means to do something, if no other method is available.

J. J. Horner
Linux, Perl, Apache, Stronghold, Unix
jhorner@knoxlug.org http://www.knoxlug.org/

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.