Re: CSocket, best way to wait for a reply?
- From: "Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp>
- Date: Mon, 11 Apr 2005 08:43:49 -0500
simon wrote:
My problem is more to find who made the original send request.
Assuming that the user opens a new screen that prints the details of user "XYZ", the screen would send a request "Who is 'XYZ'" but then I would I route the reply all the way back to that original screen so that it can repaint itself. What if two screen send the same request? how will I know what screen needs the info.
Simon
One way is built in to the MFC doc/view architecture: UpdateAllViews. If you wanted to use this concept the server reply could be examined by each view. If you are using dialogs you could implement the same type of communication yourself.
-- Scott McPhillips [VC++ MVP]
.
- References:
- CSocket, best way to wait for a reply?
- From: simon
- Re: CSocket, best way to wait for a reply?
- From: Joseph M . Newcomer
- Re: CSocket, best way to wait for a reply?
- From: simon
- Re: CSocket, best way to wait for a reply?
- From: Scott McPhillips [MVP]
- Re: CSocket, best way to wait for a reply?
- From: simon
- Re: CSocket, best way to wait for a reply?
- From: Joseph M . Newcomer
- Re: CSocket, best way to wait for a reply?
- From: simon
- Re: CSocket, best way to wait for a reply?
- From: Scott McPhillips [MVP]
- Re: CSocket, best way to wait for a reply?
- From: simon
- CSocket, best way to wait for a reply?
- Prev by Date: Re: multiline edit box
- Next by Date: Connection and retrieve image from scanner
- Previous by thread: Re: CSocket, best way to wait for a reply?
- Next by thread: Re: CPU usage, memory and virtual memory
- Index(es):
Relevant Pages
|