Re: WM_COPYDATA
- From: Hans-Peter Diettrich <DrDiettrich1@xxxxxxx>
- Date: Tue, 11 Sep 2007 07:03:57 +0200
Maarten Wiltink wrote:
The normal solution is to serialise your objects and send not the
object, not a reference to it, but data that allow a copy to be
reconstituted at the other end.
Similar to the SendImage example in Gajics code?
Very probably, yes. I haven't seen the code but serialisation is a
well-known technique, and well-suited for sending images. The important
bit is to reconstruct the picture. The object involved don't really
matter.
Perhaps it helps to see "serialization" in two distinct ways:
1) send an object type and data (unidirectional, for cloning)
2) send an object reference, describing a server application and an object identifier, for interaction with a shared object (COM, Corba...).
Where COM, DCOM, OLE, ActiveX etc. are widely used as synonyms for Microsoft/Windows shareable object model and instances. References frequently are implemented and exchanged as handles, which are handled by Windows as appropriate (e.g. locally in shared memory, globally in distributed processing).
DoDi
.
- References:
- WM_COPYDATA
- From: jimbo
- Re: WM_COPYDATA
- From: Maarten Wiltink
- Re: WM_COPYDATA
- From: jimbo
- Re: WM_COPYDATA
- From: Maarten Wiltink
- Re: WM_COPYDATA
- From: jimbo
- Re: WM_COPYDATA
- From: Maarten Wiltink
- WM_COPYDATA
- Prev by Date: Re: Look & feel Borland Delphi 7.0
- Next by Date: Re: Look & feel Borland Delphi 7.0
- Previous by thread: Re: WM_COPYDATA
- Next by thread: Re: WM_COPYDATA
- Index(es):
Relevant Pages
|