Hi,

Client-server uses a binary client and a web product uses a
browser-based client.

The fundamental client/server model features a system with only two
actors playing their roles at the two ends of the network: the client
and the server. This is known as "2-tier" architecture. It is
inherently stateful--that is, both the client and server retain
internal information from one exchange of information to the next.
However most client-server applications add a database, middle ware
layers, load balancers, and other back-end processes which make them
more technically multitier architectures.


A web-based architecture usually distributes functionality among at
least three levels of oppartion or tiers: the web browser, the web
server, and a back-end database. It is built on top of the HTTP
protocol, which is stateless: it doesn't retain internal information
between the exchange of information. Communication usually originates
from the browser side with a get or post request (a page is
submitted). The server parses that information and it is sent back to
the address that requested it. The assumption is that the request
arrived correctly. This means that there's no natural way to
synchronize the client's request and the server's response and
trickery such as user IDs, session IDs or cookies have to be employed
to simulate state.

A web-enabled system is a client-server system with a superimposed
module that provides a web interface. Client access requires software
installation on the client side, which is not true for a true
Web-based architecture.

Thanks
Vadivelan.V