>
>Thomas,
>
>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...
Because the registry offers one thing the file system doesn't: Atomic
operations. Only one process is allowed to read from/write to one key at a
time. Of course, you can do the same thing with mutexes and files, but if
Microsoft abuses the registry it must be "ok" for everyone else to do
it...right? (note the insincerety...)
You missed addressing shared memory. Shared memory is one of the more
interesting concepts, but the OP is probably better off with named pipes if
not sockets. I still say sockets are the best for data communication as
you have a better chance of porting the application to another platform
successfully.
>- Process-level hacks & Remote thread injection: ...if you want your life
>going harder...
But of course!
Thomas J. Hruska
[EMAIL PROTECTED]
Shining Light Productions
Home of the Nuclear Vision scripting language and ProtoNova web server.
http://www.slproweb.com/
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.
