Henk de Koning <henkkCOMPLEXIT.COM> claimed...

> I have an implementation of fire and forget on NT4 hanging
> around here somewhere.

> Basically just implemented a custom channel that always
> returns SERVER_UNAVAILABLE. I hook a interceptor to a
> proxy to the custom channel and a stub to the real object.
> Interceptor feeds the invocation frame into the proxy,
> the proxy calls SendReceive on the channel, the channel
> returns an error and the proxy gets rid of the invocation
> frame. Meanwhile I saved the RPCOLEMESSAGE and feed it
> into the stub later.

This sounds like it could be used to build a component for
multi-casting outgoing calls, by feeding the RPCOLEMESSAGE
into *several* stubs later. This would be quite handy for
servers that offer sink interfaces. (A problem with such
servers is that one dozy client can reduce the "liveness"
of the whole system by not returning in a timely fashion.)

I presume it would also be generic, since the details of
the sink interface will have been handled by the proxy that
marshalled all the parameters into the RPCOLEMESSAGE.
(I'm also presuming that the RPCOLEMESSAGE is either copyable
or reusable with multiple targets.)

Have I understood you correctly?
Am I being amusingly naive?
Are you willing to make the code avaiable?

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]