.asp or java versus client-server

[Vinnie the Rat]

I know there should be a lot more to qualify this, but I'm trying to defend
web development (in general) over the client-server method of connecting to
a database (and that would be ODBC, and whatever other methods that I'm not
aware of). I've been told that "in some instance" client-server is faster
than access through http. I think they are wrong - probably preaching to
the choir here, but I need some ammo, please folks.

[Tim Williams]

Vinnie,

The answer is, as usual, "it depends".
It (speed) would depend on
the amount of data transferred per connection
the relative locations of the client,server and database
the server-side technologies
the client-side technologies
the relative skills of the web vs. client-server developers

However, speed (unless terrible) is only a small part of the overall
"experience". The other issues (eg. available skillsets, interface
functionality requirements, deployment requirements) are likely to be
more significant than just speed.

If someone proposes one situation in which client-server is faster
than a web app they may be correct and be able to provide performance
figures to demonstrate. However, this isolated context may be
irrelevant to the project as a whole.

Tim

"Vinnie the Rat" <chokedee@eastnet.com.cn> wrote in message
news:O$LQHtz4DHA.3360@tk2msftngp13.phx.gbl...

> I know there should be a lot more to qualify this, but I'm trying to

defend

> web development (in general) over the client-server method of

connecting to

> a database (and that would be ODBC, and whatever other methods that

I'm not

> aware of). I've been told that "in some instance" client-server is

faster

> than access through http. I think they are wrong - probably

preaching to

> the choir here, but I need some ammo, please folks.
>
>

[Mark Schupp]

I would say that in almost every instance a "traditional" client-server
application would be "faster" since it is normal to maintain a database
connection during the entire time the application is running whereas it is
normal (in ASP at least) to disconnect and re-connect with every page. Also
add in the overhead for processing an HTTP request every time you want data
and web-apps have a definite disadvantage.

That said, performance for a single user is usually not the overriding
factor. Here are a couple of things to think about.

"traditional" apps:
-usually tie up a database connection for each user, so how many concurrent
users will your DB server support?
-will have to have DBMS software on each client, are you willing to maintain
all that?
-usually have a smoother flowing user interface.

web app:
-usually tie up a database connection only while a page is processing,
should be able to support many more "concurrent" users.
-require only a web-browser on each client
-usually have a clunkier (request page, wait, display page) user interface

--
Mark Schupp
Head of Development
Integrity eLearning
[url]www.ielearning.com[/url]


"Vinnie the Rat" <chokedee@eastnet.com.cn> wrote in message
news:O$LQHtz4DHA.3360@tk2msftngp13.phx.gbl...

> I know there should be a lot more to qualify this, but I'm trying to

defend

> web development (in general) over the client-server method of connecting

to

> a database (and that would be ODBC, and whatever other methods that I'm

not

> aware of). I've been told that "in some instance" client-server is faster
> than access through http. I think they are wrong - probably preaching to
> the choir here, but I need some ammo, please folks.
>
>

[Bob Barrows]

Mark Schupp wrote:

> I would say that in almost every instance a "traditional"
> client-server application would be "faster" since it is normal to
> maintain a database connection during the entire time the application
> is running whereas it is normal (in ASP at least) to disconnect and
> re-connect with every page.

With connection pooling, this is not as big a factor as you are making it
out to be. I know you did not indicate how much faster you were taliking
about, but somebody reading this via Google might leap to the conclusion
that they should avoid closing and reopening their connections due to the
performance hit, which is just not the case.

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.