decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Is middleware an adapter? | 113 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Is middleware an adapter?
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 | # ]

Different kinds of middleware
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 | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )