|
Authored by: Anonymous on Monday, November 26 2012 @ 09:35 PM EST |
I've always thought of middleware as being an adapter as for electrical sockets,
especially when it comes to Java. You don't have to worry about the operating
system when writing your program because the adapter takes care of that.
I think I'm seeing that it is more than that when it also becomes an extension
of an operating system.
Does this make sense?[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Tuesday, November 27 2012 @ 06:18 AM EST |
Middleware today basically provides a bridge
between stateless
connections (http) and stateful
connections (database).
Your
description is for a different kind of Middleware that sits between a web server
and a back end database, all three of which could be running on three completely
separate servers, each of which could actually be running a completely different
Operating System. Your Middleware has nothing to do with the Middleware that is
being discussed in this article.
The Middleware being discussed in this
article sits between an application and the operating system on the same
computer. An example would be java, which can be compiled to run on a number of
different types of computer hardware that run a number of different Operating
Systems, but which provides a standard set of APIs to all java applications, and
allows any java program to run on any computer hardware running any Operating
System, so long as java has been compiled to run on that Operating System on
that hardware.[ Reply to This | Parent | # ]
|
|
|
|
|