Re: Background Processing in an MFC application

From:

"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 06 Jun 2007 21:20:13 -0400

Message-ID:

<hYidnWiGaPjJwPrbnZ2dnUVZ_vmqnZ2d@comcast.com>

KeepFaith wrote:

Thanks to all. I actually meant Threads or Named Pipes.

Current:
1. The user clicks "Send" in another dialog. The "OnClick" event will
send the file and push this file to a temp directory.
2. The user is also given another dialog which actually displays the
files in this temp directory. The user can select and click "Delete".
We want to do some automation and would like to delete the sent
files automatically (but only after successful "send").
3. Just before deleting the file, the code need to open the same in
"Adobe Reader" to get some line/word counts.

Proposed:
1. The "Send" function will send a message (to the named pipe) after
successful "Send" for deletion.
2. The named pipe will open the file in Adobe Reader and get all the
details.
3. The same named pipe will then delete the file.

Is this all part of one program? If so then using named pipes, and
perhaps even using files, is adding a lot of unneeded complexity.
Different parts of your program can communicate and pass data without
needing to use intermediate files and pipes.

And I share Joe's confusion about several of your statements. I think
we need to understand the situation better before we can offer any
pertinent suggestions.

--
Scott McPhillips [MVP VC++]