Passing data between filepro tasks
Kenneth Brody
kenbrody at spamcop.net
Fri Jun 17 14:34:43 PDT 2011
On 6/17/2011 3:11 PM, Brian K. White wrote:
[...]
> Similarly, on unix you can write and read to/from a named pipe but not
> on windows.
Although I've never actually used them, Windows does have named pipes.
> I'd just go ahead and use the file. It's not _that_ bad in terms of
> programming work especially once you do it a few times. And the OS and
> hardware will mostly magic-away the inefficiency of creating, writing,
> reading, deleting a file thanks to caching. And it'll work the same
> everywhere. And if the processes are both filepro, and both in the same
> filepro directory, then it's even simpler since the intermediary file
> can be a filepro file and you're using lookups instead of raw file i/o
> commands.
Expounding on that idea...
Create a filePro file with a single memo field. From the main file,
lookup-free to create a record, and WRITE it. Pass the record number via
one of the -r* flags. In the child process, write the return info into that
record's memo. When back in the parent, re-read the record, grab the info,
and delete the record.
--
Kenneth Brody
More information about the Filepro-list
mailing list