Virus said:
Duane Arnold wrote:
What does .net have anything to do with it?
..Net and Java do the same thing in the principles of how Web based
solutions work when it comes to multiple versions of the runtime
components on the client workstation, which is going to be based on what
runtime version of either solution (.NET or Java) that executes at the
WEB server.
When the Web server sends HTML controls to the browser to execute and
then the page is sent/posted posted back to the Web server to execute,
it is based on what the Web server is sending and wanting back.
The client side must be in sync with whatever is being used at the Web
server. Web servers on the Internet when it comes to using Java or .NET
solutions are not and do not use the same versions of the runtime
components. A Web server at a company can be using one version of the
runtime components while another company's Web server can be using a
different version of the runtime components.
If a system does (or does not?) have the .net thing installed, and if
it does have multiple versions of JRE, then again I ask this simple
question:
It's obvious that you don't know about Web base application development
and how things work between the client side browser and the Web server side.
If HTML code (or Java code or class code or other java crap code) is
retrieved by a browser during casual surfing, then can (or IS) said
code processed/executed/rendered/handled by a specific version of the
JRE ->as dicated by data in the code<- ????
What data are you talking about? Yes, there is data being sent or posted
back that is encapsulated in HTML controls that may or may not be
visible to the end-user, enterable by the end-user or selectable by the
end-user.
The browser on the client side doesn't retrieve anything. The page is
sent to the browser by the Web server and the browser sends/posts it
back to the Web server.
You have client side code in a page that the Web Server sends in a WEB
session to the browser to execute when the page is rendered at the
client machine. There are server side code/HTML controls in a WEB
session that only work at the Web Server when the page is posted/sent
back to the Web server.
Everything is based on what version of the runtime components at the Web
server that are being used, as it's the Web server that sends the page
the browser is to execute. Newer version of Java or .Net are backwards
compatible with older versions. So things run smoothly or transparently.
But if a Web server sends a HTML control that is based on a newer
version of the runtime Web server components and the newer runtime
version is not on the client side that is needed to render the HTML
control on the page, it's not going to be able to render the HTML control.
It's all based on what version of the Web server runtime components are
being used to render the page at the client machine's browser. And Web
servers out there on the Internet are not in sync with runtime versions.
Web solutions are based on what version of the Web runtime components
are being used in the development of the Web solution by the developer.
The bottom line is there are going to be multiple versions of the
runtime components on the client side.
And what I mean by send and post back in a Web Session is that the Web
server sends a page and the connection is terminated with the client
machine. It's a stateless session.
Then client machine browser posts back to the Web server the page and
then the Web server has to figure out who you are with the Web page that
was posted back, which may or may be done by the use of cookies or other
controls hidden or transparent to the end-user on the page.
The Web sever has multiple stateless sessions with a client or a
stateless session every time a page is sent to the browser and is posted
back by the browser. That way, the Web server can have multiple clients
in stateless sessions.
Duane