Xref: utzoo comp.lang.c++:5672 comp.object:506 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!cimshop!davidm From: cimshop!davidm@uunet.UU.NET (David S. Masterson) Newsgroups: comp.lang.c++,comp.object Subject: Re: Shippable C++ Objects (RFC) Message-ID: Date: 28 Nov 89 07:30:51 GMT References: Sender: davidm@cimshop.UUCP Organization: Consilium Inc., Mountain View, California. Lines: 23 In-reply-to: cimshop!davidm@uunet.UU.NET's message of 15 Nov 89 18:10:37 GMT In my previous article, I requested comments on an idea for shipping objects between processes. Having had a little time to play with the idea, I have found a flaw in the methodology. The problem concerns container classes of virtual objects and that a receiving process would not know what type of object was contained within the container it was requested to reconstruct. The wish is that the container class should only know about the base virtual object that it might contain -- not any of the possible derived children. Part of my idea was based on the feeling that a receiving process, once informed of the incoming object type, would know what to do with the incoming stream. The virtualness of internal objects in the stream means there are more decision points than this idea could handle. Oh well, back to the drawing board... ...maybe extending the event callback methodology for both internal and external events... `:-/ -- =================================================================== David Masterson Consilium, Inc. uunet!cimshop!davidm Mt. View, CA 94043 =================================================================== "If someone thinks they know what I said, then I didn't say it!" Brought to you by Super Global Mega Corp .com