Re: VCL.NET or ASP.NET tools

* _porting_ to an asp.net-only web app. No more kbmmw. Or:

ok... but if he has requirement for an n-tier solution today, Im pretty
sure he would still want to have that regardless
of if the executing machine is IL based or Intel based.

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.

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.

In a pure asp.net app, he wouldn't use kbmmw. Or at least, I can't see
any
reason why he would.

Several reasons:

- 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.

- 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.

- 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.

- 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.

I really didn't intend this as a 'kbmmw can't have asp.net web front
ends'.
Of course it can. I was just trying to help the guy figure out what he
wants, and to take the best action accordingly.

I understand. I am just explaining that kbmMW isnt 'limited' to Win32 only
server or client side

ok . . .

and that ASP.Net do not
change any of the basic requirements of any largish scale setups.

I don't know what you mean by that. Adding an asp.net front-end doesn't
change any of the basic requirements?

Regards

Lauchlan Mackinnon



.

Relevant Pages

  • Re: Help with first VB application - Data Entry form
    ... I assumed a desktop / winform client application ... time' stamp from the database machine - control machine ... ... problem solved - web server is control system. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help with first VB application - Data Entry form
    ... I assumed a desktop / winform client application ... time' stamp from the database machine - control machine ... ... problem solved - web server is control system. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Remobjects v KBM
    ... >> client query components) follow from that. ... Then, connections can be created to say SQL Server, Oracle, Interbase and ... can then be created from the abstract dataset definition in 'customers' to ... implicitly - this makes your code not be database connection specific). ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Help with first VB application - Data Entry form
    ... stamp from the database machine - control machine ... ... unnecessary data to the client ... ... and when building a database independent UI / Client - Server application, ... JavaScript, for example) and thus, will get the time from the web server, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Opinions needed about the best "Middleware suite" kbmMW vs. RODA
    ... kbmMW supports cross db in such way that all you need to do in your application is to set one property to switch to ... What one have to concentrate about is minimizing the amount of data moved from the app server to the client. ... C/S setup's usually have a quite active chatter going on between the client and the database, ...
    (borland.public.delphi.thirdpartytools.general)