Hi,

I am looking to build a solution whereas I load a large dataset via a
Windows Service and then make that dataset available to my other
applications via .NET Remoting.  My other applications connect through
web services and loading the data over and over again is a lot of
resources and adds a time expense to each call.

When I went to implement the solution I found that everything worked
fine, except that when my application  remoted into the windows
service the first time the remoting object was actually loading the
data.  After the initial call the time to query the data dropped (from
8 seconds to 1 second). I am trying to avoid the first call and any
subsequent call from taking 8 seconds or longer.

But shouldn't my application be able to query the windows service for
the already loaded data in 1 second?  The windows service shows it is
loading the data.

Is this possible via .NET Remoting or should I be looking at another
option.  I have opted to serialize the data to disk and have my
applications pick up the serialized dataset (this takes about 2
seconds)... however I would like to have this work through remoting.

I have not used .net remoting that much so I may have missed something
when I initially wrote the solution.

Any suggestions or comments are welcome.

Greg