Re: [MacPerl] rcp using MacPerl?

["Jon S. Jaques" <sysadmin@almus.com>]

In my experience with Macs and anything internet, or anywhere where information shall be shared with
anyone else, filenames should follow convention, anyhow. Because the Mac does not 'enforce'
'correctness', terrible things can accidentally be embedded into filenames such as references to
physical hardware devices on the host computer, not to mention potential system commands. Sometimes,
if these files ARE allowed to be placed onto a non-Mac  server, there can be serious problems; data
loss and/or the inability to access/delete offensive files can be the least of these! (I know from
experience!)

Do yourself and your administrators a favor, and use underscores and dashes ( _ - ) instead of
colons, slashes, bullets, spaces, etc. If you use these compatible filenames ALL of the time, then
you will NEVER have difficulties of this sort when publishing your data.


--Jon S. Jaques

>Here's the problem: my ISP (an otherwise very good service provider) disables spaces and other
special characters when uploading files via ftp. They claim it's for security and that most other
places do it as well; my experience has been otherwise (they're the first out of more ISPs than I
care to count). But that's irrelevant because I'm not switching and they're not changing :*)
>
>I need to have spaces and other special characters in my filenames; I have hundreds of files and
simply let Apache do the listing of directories, and I want them to be in human-readable form.
>
>I know that rcp to their system allows full filenaming. On Unix, of course, I'd just call rcp. Has
anyone implemented rcp for MacPerl?
>
>Is there another (perl or otherwise) solution that I'm overlooking?
>
>What I'd like to do is just create an app that I can drag files onto and have them copied to the
web server. Everything's a snap except for the actual transfer. I haven't been able to find an rcp
implementation for Perl, probably because it makes no sense to create one on Unix perl when you can
just call rcp...
>
>Some of the other wild solutions I've discarded are making it a drag-and-drop *e-mail* perl app,
encoding the destination of the file as a header, and then using procmail to put it in the right
place. Or, having the perl app ftp over the file after encoding the special characters, and dropping
another file into a special location that lists the files that need to be copied and where they need
to go. Both seem overly complicated :*)
>
>Jerry
>
>jerry@acusd.edu                                           http://www.acusd.edu/~jerry/
>"It's too bad we don't have a can to listen to to get back to San Diego," said Voniece. "What do we
make in San Diego, anyway?"
>"Tourists, I think," said Arthur. He brightened. "Do they sell tourists in cans?"
>"I think they do," said Voniece, "but they're awfully expensive."
>--The Shopping Cart Graveyard
>
>
>
>***** Want to unsubscribe from this list?
>***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch
>


***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch