I don't know if 'zzz' want to do some exercise on sockets, my tip was just
to let life easier! :)
I use sockets for distributed client/server applications but not if I
simply need to share memory with two or more processes on the same machine.
- Pipes: just like file mapping, you're right, may be they are easier to use
- COM/DCOM: nothing for newbies but a real amazing world...
- DDE: used once in my life... hoping not to get in touch again!
- Registry: well, why don't just use a simple file...
- Process-level hacks & Remote thread injection: ...if you want your life
going harder...
Cabbi
At 11:23 30/11/2004 -0500, you wrote:
>At 05:08 PM 11/30/2004 +0100, Fabio Cabella writeth:
> >
> >Are you sure that sockets are your final choice?
>
>Sockets are the generic choice and allow for the most flexibility. Of
>course, with flexibility comes a performance tradeoff. Once a
>communication mechanism is written, however, it should only need to be
>written one time.
>
>
> >If the two applications are on the same computer there are some easier ways
> >to exchange data:
> > - WM_COPYDATA
> > - File mapping
>
>You missed a couple other ways:
>- Pipes
>- COM/DCOM
>- DDE
>- Registry abuse (i.e. NT performance monitoring does this).
>- Shared memory.
>- Process-level hacks.
>- Remote thread injection.
>- And, of course, a little magic.
>
>
>Thomas J. Hruska
>[EMAIL PROTECTED]
To unsubscribe, send a blank message to <mailto:[EMAIL PROTECTED]>.
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/c-prog/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
