The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.

The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.

The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.

The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.

The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.

Joe Winchester's Java Blog: Rich Client, Poor Client, Cool Client, AJAX. The problem with the web has always been that despite anyone trying to convince you otherwise, it's a page based latency bound transaction model that is a dressed up graphical mainframe. Works well because the transport protocol is neutral and ubiquitous allowing heterogeneous end points where the client and server don't have to know all that much about each other, just how to establish an HTTP connection. Problem with web is that if all the logic occurs on the server back end app, then the client is relegated to being just a dumb renderer of HTML, which sort of belittles the fact that PCs are pre-emptive multi-tasking box with oodles of processing power.