Content deleted Content added
No edit summary |
|||
Line 146:
I came to this article while trying to find out a little about [[Android (operating system)]] to understand more about how my husband's new Android-based phone is different from my new iPhone; the early paragraphs of that article referred to "middleware," which was a term I'd never heard. To dig deep into a concept like middleware, I accept, I would need to get used to complicated tech-talk. However, I still maintain that the first paragraph or so of this sort of article still should offer something that the casual reader/user might at least have a chance of comprehending at least partially. Can we not try again, here? [[User:Lawikitejana|Lawikitejana]] ([[User talk:Lawikitejana|talk]]) 12:58, 14 June 2011 (UTC)
In my 15 years I've used the term 'middleware' to describe the software layer underneath the application which provides services specific to the type of application. For instance take a cell phone software stack - the middleware would provide everything from task creation to graphics support, input management to phone features, etc., encapsulated with a consistent API. It's like a collection of libraries that share a common style and are designed to work together. Usually it sits on top of a hardware/os abstraction layer.
| |||