Re: Never ending programs

Rob

>What they mean is that you have a very simplistic trigger program that
>calls another program and passes/receives the buffers.  This way you can
>make changes to the called program without having to get an exclusive lock
>on the file involved.

Bucks example handled/explained this pretty well.

>Perhaps what you meant was the people who have trigger program call
>secondary program which then passes the buffer to a data queue.  Then, in
>that case, you would have a NEP to process the data queue.

Actually this is exactly what I was thinking - mainly because I was
thinking of very heavy use of a trigger and a never ending program seems
like a good way of handling this.

I should have thought of trigger in the more generic sense :)

Regards
Evan Harris