Groklaw - Digging for Truth

	When you want to know more...

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

You won't find me on Facebook

Donate

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:

On servers donated to ibiblio by AMD.

Webmaster

In your case, the JVM is the middle ware. | 113 comments | Create New Account

Comments belong to whoever posts them. Please notify us of inappropriate comments.

In your case, the JVM is the middle ware.

Authored by: jesse on Tuesday, November 27 2012 @ 07:50 AM EST

There are all kinds of middleware - The X intrinsics are one - it layers between
the OS and the X server providing communication services AND an interface
reasonable for GUI implementation.

In most cases, various toolkits are also middleware - they provide more advanced
interface between the GUI and the X intrinsics...

The same can be said of the C runtime library - it provides easy to use layer
between applications and the local operating system, and is used by nearly
everything layered on top - such as the X intrinsics... and the toolkits layered
on top of them.

The term "middleware" came about by software vendors
creating/extending other vendors libraries, usually the "middleware"
was targeted to a specific problem domain, and usually included
"portability" between multiple implementations of lower level
software.

[ 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 )