Re: VCL.NET or ASP.NET tools



But just about any web application is already n-tier, in a sense. You
have
an application server. You have a thin client (browser) with little if
any
business logic on it. The business logic is centralised on the server.
You
can partition the logic into tiers as required on the server.

[ . . . snip . . . ]

Hence an application server _is_ in use. Its just under another name.

I thought that was exactly the point I had made! A web application already
has an application server. You need an application server to provide
data-driven web applications that server HTML pages dynamically created on
the fly.

That application server could just as well be kbmMW or competing 3rdparty
products for .Net. Doing that would save you
alot of coding, and give you a setup that is easier to maintain, have more
out of the box features and are readily
available for scaling from the smallest to the largest setups without
changing code.

Alright. You could make your webserver use kbmmw as an ISAPI dll or
something. Why not?

But my point was why would you , in the case where there are only browser
clients? I don't see any advantage. It seems to me that it just adds
complexity, and does not make it easier to maintain.

What an n-tier solution like kbmmw provides that I think he *won't* need
in
a web application is mechanisms for managing/resolving deltas of data,
because he can't embed a kbmmw client in a web browser (AFAIK, anyway).
He
will be most likely transmittingdata through form variables, URL
variables,
etc and receiving it as e.g. sent in grids or control values on an HTML
page.

Essentially you have a 4-tier solution. db - appserver - webserver -
browser.

4 tiers is still covered by 'n' tiers, I think! <g>

- He want scalability towards backend.

You get that anyway. ASP.NET or Cold Fusion web apps, for example,
arrchitected correctly can happily have server farms and seperate
database
farms.

Cold Fusion provides app server bits of its own. ASP.Net provides app
server bits in the form of COM+ objects and
optionally MTS or MSMQ-
You do have an app server in the mix even if you dont think about it.

Right, I know they both have app servers. That is exactly why I was
mentioning them as examples of n-tier applications. I don't follow your
point . . .

- He dont want to be limited to a specific database API (ADO.Net in the
standard case).

He isn't anyway. The database is all on the server side. If you want to
use
a different database, you just change it in the server.

As long as ADO.Net supports that db. You dont have the choise to swap in
_any_ api that is not easily supported by
ADO.Net by the flick of a property setting.
You do with kbmMW.

Sure, you support whatever databases the web application framework supports.
For Cold Fusion, that's any database with an OLEDB or ODBC interface. That's
a lot of databases. For ASP.NET it's any database with an ADO.NET provider.

Really, I don't think changing databases frequently is typically an issue
for a web application. You are in control of the back-end, typically you
make the database server choice that suits you once and then stick with it.
Changing database servers every week is normally not desired.

- He want to have all the caching facilities he can get because his
site
gets hundreds of thousands of hits per day
(guessing ;)).

He can happily do that in platforms such as ASP.NET or Cold Fusion.

Yes... he could even do it in assembler code. But his choise is _to code
it himself_. Why reinvent the wheel?

No, I meant caching is built in to both ASP.NET and Cold Fusion. It's not
re-inventing the wheel, it's using the features provided out-of-the-box.
Your reference to assembler seems irrelevant to me. At least, I do not see
its relevance . . .

- He want _other_ type clients to be able to access his data.

What do you mean? For a web app, the clients are browsers. Period. But
if he
wants to make it available to other clients, he can just use web
services.
And he can happily do this in ASP.NET or Cold Fusion.

His current application have some business code in it. Im sure he dont
want that business code being tugged away
(embedded into) an otherwise not accessible application in the case MS
invents something new after ASP.Net or IBM comes
up with a new paradigm/product.

ok. He would be porting that business code to the web app.

Lauchlan M


.



Relevant Pages

  • Re: Prolog on a web server
    ... thrilled if you wanted to load it all into server VM:-/ ... rapidly build yourself a desktop app (Delphi? ... As for Prolog, it could surely be the basis of a decent ... grown-up database query language (an open standard dialect ...
    (comp.lang.prolog)
  • Re: Python Database Apps
    ... It's gonna be a desktop app. ... so that I don't need a database server on the client side. ... If you have an offline mode then the most important thing to work out ...
    (comp.lang.python)
  • Create SharePoint Portal failed.
    ... One mentioned ensuring that SQL Server uses a case ... 13:55:40 Service database server is 'USDC-JOHRIV'. ... Update dbo.propertylist set DisplayName = N'Last name' ...
    (microsoft.public.sharepoint.portalserver)
  • Re: HELP PLEASE - need app to modify multiple MDB table designs simultaneously
    ... ONE database runs ONE application and EACH ... application runs only ONE web site and it work great this way. ... particular app, it would not be efficient to have ONE application run ALL ... web sites on my server. ...
    (microsoft.public.access.replication)
  • Re: HELP PLEASE - need app to modify multiple MDB table designs simultaneously
    ... ONE database runs ONE application and EACH ... application runs only ONE web site and it work great this way. ... particular app, it would not be efficient to have ONE application run ALL ... web sites on my server. ...
    (microsoft.public.vb.com)