Re: Urgent... RPC Function

I ask my questions on this list and invariably get answers within the
hour.  How much more quickly do you think writing Urgent will make us
answer your questions?  Especially when the question is about DCOM (and
I suspect cross posted to ATL and DCOM lists).  Please don't put urgent
in your subject lines.

Thanks,

Shawn Wildermuth
[email protected]

> -----Original Message-----
> From: The DOTNET list will be retired 7/1/02
> [mailto:[email protected]] On Behalf Of Yogesh Shetty
> Sent: Monday, June 17, 2002 5:36 AM
> To: [email protected]
> Subject: [DOTNET] Urgent... RPC Function
>
>
> Hi,
>
> I am facing a peculiar problem...
>
> The deployment is Client - Server solution using DCOM over
> Leased Line Network ( <= 64 MBPs). Protocol used  - TCP / IP
>
> The DCOM Server uses QueueUserWorkItem (ThreadFunc, NULL,
> WT_EXECDEFAULT) to send messages to client asynchronously.
>
> THE PROBLEM -
> The DCOM Server generates messages in rapid succession ( in a tight
> loop) for client. However, the client does not receive all
> those responses. When sniffed on Server side, it was observed
> that the DCOM server did not send ( or dropped ) many
> messages to client. Has any one faced such a problem? Is
> there any problem in calling QueueUserWorkItem in a tight
> loop? Especially, on slow networks? (Note - It works on LAN
> i.e. baud 2MBS and above.)
>
> Any help in this regard is highly appreciated
>
> You can read messages from the DOTNET archive, unsubscribe
> from DOTNET, or subscribe to other DevelopMentor lists at
> http://discuss.develop.com.
>

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.