[JDEV] JabberCOM in C++: The problem ...

[David Waite]

> > From: Scott Francis [mailto:sfrancis at blueairnetworks.com]
> > Sent: Friday, May 25, 2001 5:05 AM
> > Subject: [JDEV] JabberCOM in C++: The problem ...
> [snip]
> > The reason you can't use ATL to implement IDispatch for you is
> > because the event interfaces in the JabberCOM IDL are not defined
> > as dual (why?). Therefore, you basically need to have a massive
> > switch statement in your IDispatch::Invoke() method, checking
> > the DISPID's of the method being invoked.  Then either call your
> > function directly from IDispatch, or hell, make it inline.  But
> > at least it will be called.

I missed this post earlier. There is no standard way to make events dual
- being that the interface is dual, the event listener (not the
broadcaster) would end up having to implement both interfaces, which is
probably not what is wanted.

Theoretically, you might be able to have two separate event
registrations in the broadcasting component to accomplish this, though.
It would go down one list, then go down the other.

-David Waite