The Myth Of Linux Community Support. 963
Please stop building strawmen in a pathetic attempt to distract from the argument.
The Myth Of Linux Community Support. 967
An example that illustrates and supports an argument that is not under debate, in order to divert attention from the real argument, is most certainly a strawman. Haha! No it isn't. the...
I have not changed my claim. You keep building strawmen.
Strawman. This has nothing to do with what protocol is used for a transfer. There is no transfer of the application. The application server runs the application. It does not transfer it to the client.
Strawman. The client processor doesn't need to do anything with code that it *doesn't run*. In the case of a true application server, the client machine does not run the application. The *server* runs the application.
The Myth Of Linux Community Support. 964
The keyboard and mouse inputs, and the application output is transferred The file system engine on the remote machine receives files to be saved and makes files or parts of files available to the...
Strawman. The client requires no network means of opening the file, since the client doesn't open it. The "file", in the case of a true application server, is an application that is opened by and executed on the *server*. The client is not involved, other than to trigger end and send-receive its own I-O. Again, this *not* the I-O under discussion.
Strawman. Irrelevant to a true application server since the application data is *not transferred* to the client.
The *difference* here is not a matter of the protocol used to accomplish a transfer. It is a question of whether or not a transfer is even *necessary*. In the case of a true application server, no transfer is necessary other than for I-O between the client and the server which is *not* the I-O under discussion.
Strawman. The protocol used for a transfer is irrelevant, because there is no transfer.
Strawman. That only applies if the client is running the application. In the case of an application server, the application is running on the server and likely manipulates data that is not transferred to the client.
Are you forgetting that a web server can be used to trigger end of an application on the server? The client does not require a transfer of that application, and it does not run that application.
Not all I-O need be communicated to-from the client. The application runs on the server.
Look, stupid. We are not talking about I-O between the client and the application. We are talking about resources the application uses to accomplish its task *that are not communicated to-from the client*. These resources need never be transferred to the client for any reason in the case of a true application server.
Since you appear to be completed braindead, let me illustrate.
1) Application server: Client connects. Server loads appliction into its own memory along with any necessary resources, wherever they might be. Server runs applicaton, preparing any output that it *may* eventually send to the client. Application updates a database, alters other resources in some way, stores the altered resourses on the server's disk, whatever, all without involving the client. Finally the server possibly sends some output to the client. It takes 1 second for the server to run the program and complete all I-O operations with the client, because the server is a much faster machine than the client.
2) File server: Client mounts remote directory on the server. Client loads application into its own memory (requiring a network transfer). Client runs application and handles all the burden of resource Debt Management (requiring additional network transfers) that is taken care of by the server in the other scenario. It takes 20 seconds for the client to run the program, because the client is a much slower machine than the server.
If you don't see a difference here, then you are retarded.
To sum it up, you are either a blockhead or a troll.