The problem I am having is when my app is run at remote sites. The DB is on
a server here at our main office, but the app is out at various sites and the
performance out at these sites is very poor. A search that takes 8 seconds
here is taking 1min 5seconds out at site! Some of this could be the line we
have between the site and here, so I am thinking that if all the processing
was done here on the server, then I could just spit back the dataset. Is
this what remoting is for?
Thanks
Steve
"Norman Yuan" wrote:
The thing you referred to might be COM+, which can still be used in .NET
app. In pure .NET world, though, the equivalent would be Remoting and Web
Services, or Window Communication Foundation (WCF) in upcoming .NET3.0
"Steve" <St***@discussions.microsoft.com> wrote in message
news:68**********************************@microsof t.com... Windows Visual C# / SQL Server 2000
I am new ish to the .Net world of development, and am sure this is a
pretty
basic question, but I'll ask anyway.
In my past development experience (Progress) we had a technology called
AppServer. Basically all the business logic runs on the server where the
database is, and the screens on the client have no references to the DB at
all, but instead run code on the server, which returns the data for the
screen.
What is the .Net world equivalent to this?
Thanks
Steve