Hello Kevin
Remoting through IIS, while easier to sucure than direct TCP/IP remoting is
drastically slow compared to direct connections. Are you working across a
secure network? If you are then get away from IIS and use Direct TCP/IP
remoting instead. If you are going to go across the Internet with your
remoting then you wil have to provide some security of your own devising.
The performance curve compared to what you are now using is quite
signifigant. If you have to stay with IIS hosted remoting, then use
ws_HTTP_Binary. Again, more work on your part, but some perfomance gain
over (I hope you are avoiding) the SOAP protocols.
If it's raw performance in a remoting environment that you need, then TCP
Remoting is it. Read this article:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/introremoting.asp
There are some performance charts that might interest you.
--
Ibrahim Malluf
http://www.malluf.com
==============================================
MCS Data Services Code Generator
http://64.78.34.175/mcsnet/DSCG/Announcement.aspx
==============================================
Pocket PC Return On Investment Calculator
Free Download
http://64.78.34.175/mcsnet/kwickKalk1.aspx
Kevin Cabral said:
I am using .net remoting and IIS to get datasets back from the database.
For each listbox on a form that is filled with code values, the process
takes ~1 second per listbox. The performance is significantly better (about
1 second to load the form with all the data) by using a dataconnection and
datasets from a form but I'm concerned about scaliblity issues later on.
Does anyone have any advice or an article, book, that I can get to do a
better guide? I have been researching and reading .net remoting, IIS, NT
services but for every one solution there's 500 other articles that makes it
difficult to find a common thread. I am writing the system in C# with
Sqlserver and Window forms. Thanks