First, please see my post in
this thread.
Quote:
Originally posted by Neo
Here is another question:
With N-tier web application services and publish-subscribe architectures in the picture, what are the current layered protocol stack (complexity management) models?
Stuff like this does not modify the basic networking protocols. Rather, it imposes much more order on the application layer. The three tier model, which my company now uses, says that the user should not need a special client for your application. Instead, the user should just use a local web browser. Next, the user should not be expected to learn sql or anything like it to search a database. Some kind of easy to use middleware should interupt the user's needs and figure out what to do. That front-end to our database is complex and multi-layered itself. But we still call the whole concept a three tiered approach.
In the old days, we would have delivered special client software to our customers with its own user interface. And some skill would be needed to search our database. Now our customers just use a web browser and this alone shortens the learning curve. And you could probably teach Lassie to search our database...no sql or anything.
But the whole shebang is running on TCP/IP which has not changed. I don't know what publish-subscribe means, but I doubt that it modified TCP/IP either.