"Stewart Rogers" <StewartRogers@discussions.microsoft.com> wrote in message
news:53E06504-3877-4BCA-A434-869F224BE335@microsoft.com...
> Guys,
> My ASP.NET application (on SERVER-A) has been calling .NET remoting
> components that are hosted in IIS (on SERVER-B). So far i have been
> calling
> components in synchronous fashion where my ASP.NET page waits for the call
> to
> return.
>
> But new requirments just came and now I would have to call remoting
> components asynchronously! I know that we can call components
> asynchronously
> but :
>
> (1) I don't know how to do that. I do have the following link
> http://samples.gotdotnet.com/quickstart/howto/doc/Remoting/async.aspx but
> have not tried it yet.
>
> (2) Are there any side effects of calling remoting objects asynchronously
> from the ASP.NET? I mean I am looking for the "fire-and-forget" kind of
> approach where I will call remoting component, and then return; that way,
> my
> page will not have to wait for the component call to finish but I am not
> sure
> what will happen when the call completes and the remoting runtime calls
> the
> callback function!
>
> (3) What would happen if I specify null as the reference to the callback
> method? will my call still be dispatched to the .NET component?
>
> Any thoughts?
>
> thanks,
> Stewart Rogers