Still does not sound like a show stopper. You will definitely experience low
performance since VB coclasses are single threaded, so if you call back from
two different threads within your C++ component calls will be serialized by
COM message dispatcher.
--
Sanin Saracevic, MCP
Lead Software Architect
Interland, Inc.
Quote:
> Hmmm.... unfortunately it must be asynchronous....
> And to add some extra spice there are 4 different methods in the VC
> Component
> through which the VB Component may communicate AND 4 corresponding methods
> in the VB Component that VC uses to fire the callbacks...
> Thanks anyway
> /Johan Eriksson
> > Absolutely. Unless you are talking about asynchronous calls you can just
> > call back on that interface w/o any attention to the fact that it is
> coming
> > from VB coclass (coclass is a coclass after all in whatever language you
> > manage to write it) :-)
> > --
> > Sanin Saracevic, MCP
> > Lead Software Architect
> > Interland, Inc.
> > > I want to have a Service (VC++) which has a method (Connect) that
> receives
> > a
> > > backpointer to the caller. The problem is that the caller is a VB
> > component
> > > who passes an interface through which the VC++ program may execute any
> > > callbacks. i.e. VC++ receives a reference to a VB object..... Does
> > > anyone know if this is even remotely possible ?
> > > /Johan Eriksson