Keep in mind that Datasets get serialized as XML and this gives rise to
performance bottlenecks. You have a few options;
1. Use VS.NET 2005 and set the RemotingFromat property on the DataSet to use
binary serialization.
2. Implement a DataSet surrogate to customise dataset serialisation (see
Take a look at MS Knowledge Base Article 829740 Improving DataSet
Serialization and Remoting Performance in support.microsoft.com
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] Behalf Of Ranjan
Sent: 20 December 2004 07:09
To:
I have a client app that remotely calls a server-side component using .NET
Remoting - the server-side DLLs run in a listener implemented as a Window
Service.
I want to give the user on the client-side the ability to cancel long-running
and potentially expensive calls. How can I cancel such calls?
I have a windows service that acts as a .NET Remoting listener for incoming
requests from remote clients. I verified that the listener does actually use
the thread pool to service client requests. Now, given the fact that there are
(by default) only 25 threads available in each CPU's thread pool,
