[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

Re: [MacPerl] hotfolder mechanism



See below
--Quentin
----- Original Message -----
From: "Axel Rose (by way of Vicki Brown)" <rose@sj.com>
To: <macperl@macperl.org>
Sent: Thursday, June 29, 2000 10:17 PM
Subject: Re: [MacPerl] hotfolder mechanism


> Thanks for pointing me to the relatively new "folder action"
> scripts. There are examples available in the "Scripts"
> folder within the system folder.
>
> First I did not consider them for my task because I didn't
> like the setup of a folder action starting a MacPerl script,
> which in turn is scripting StuffIt and finally moving
> stuffed files to the destination folder with MacPerl.
>
> The example scripts employ a check for file type of "bzy". I
> haven't heard of this one before.
It is actually "bzy1", "bzy2", etc. You should just use a regexp or maybe a
substring. Basically "bzy" files are files that are still being copied.
>
> Some other considerations: A Mac sharing it's volumes via
> AppleShare gets awfully slowly if I let him poll a
> hotfolder, run StuffIt and move files around. Transfering
> files dropped from 800kBytes/s to 40k/s. Users might think
> the serving Mac is frozen. While the polling script executs
> sleep() my impression is that this costs too much
> performance. Does anybody know a better method for idling
> around in MacPerl?
Take a look at this code:

use Mac::Events;
$delay = 5; # 5 seconds
$done = TickCount + ($delay * 60)
while (TickCount < $done) {
WaitNextEvent;
}
>
>
> Again many thanks for following me
>
>
> Cheers,
> Axel
>
> > before reinventing the wheel I'd like to know whether this
> > has been done before:
> >
> > A MacPerl script is watching a hot folder.
> > When new files or folders arrive it is checked whether they
> > continue to change. After complete arrival those files are
> > further processed by whatever Mac program and put into an
> > out folder.
> >
> > The concrete task I have in mind is to use StuffIt Deluxe
> > for compressing. It's a pity that only Expander but neither
> > Deluxe nor DropStuff has such a mechanism.
> >
> > There a several minor problems for which I alreday found a
> > solution. (stat($file))[8] gives last access time which
> > continue to change until copying into the hot folder is
> > finished. Controlling StuffitDexlue with AppleScript is no
> > problem too.
> >
> > But processing dropped folders get's cumbersome. A module
> > for having the watched/hot folder mechanism seems to be a
> > common question for me though it is hard to implement with
> > all sorts of error checking. Imagine one pulls out a dropped
> > file from the watched folder or is doing a second copy to it
> > after it has been processed already.
>
> # ===== Want to unsubscribe from this list?
> # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org
>


# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org