The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems.^[1] HTTP is the foundation of data communication for the World Wide Web.

Hypertext is a multi-linear set of objects, building a network by using logical links (the so called hyperlinks) between the nodes (e.g. text or words). HTTP is the protocol to exchange or transfer hypertext.

The standards development of HTTP was coordinated by the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C), culminating in the publication of a series of Requests for Comments (RFCs), most notably RFC 2616 (June 1999), which defines HTTP/1.1, the version of HTTP in common use.

Technical overview[link]

HTTP functions as a request-response protocol in the client-server computing model. A web browser, for example, may be the client and an application running on a computer hosting a web site may be the server. The client submits an HTTP request message to the server. The server, which provides resources such as HTML files and other content, or performs other functions on behalf of the client, returns a response message to the client. The response contains completion status information about the request and may also contain requested content in its message body.

A web browser is an example of a user agent (UA). Other types of user agent include the indexing software used by search providers (web crawlers), voice browsers, mobile apps and other software that accesses, consumes or displays web content.

HTTP is designed to permit intermediate network elements to improve or enable communications between clients and servers. High-traffic websites often benefit from web cache servers that deliver content on behalf of upstream servers to improve response time. Web browsers cache previously accessed web resources and reuse them when possible to reduce network traffic. HTTP proxy servers at private network boundaries can facilitate communication for clients without a globally routable address, by relaying messages with external servers.

HTTP is an application layer protocol designed within the framework of the Internet Protocol Suite. Its definition presumes an underlying and reliable transport layer protocol,^[2] and Transmission Control Protocol (TCP) predominates for this purpose. However HTTP can use unreliable protocols such as the User Datagram Protocol (UDP), for example in Simple Service Discovery Protocol (SSDP).

HTTP resources are identified and located on the network by Uniform Resource Identifiers (URIs)—or, more specifically, Uniform Resource Locators (URLs)—using the http or https URI schemes. URIs and hyperlinks in Hypertext Markup Language (HTML) documents form webs of inter-linked hypertext documents. On the Internet the World Wide Web was established in 1990 by English computer scientist and innovator Tim Berners-Lee.

HTTP/1.1 is a revision of the original HTTP (HTTP/1.0). In HTTP/1.0 a separate connection to the same server is made for every resource request. HTTP/1.1 can reuse a connection multiple times to download images, scripts, stylesheets et cetera after the page has been delivered. HTTP/1.1 communications therefore experience less latency as the establishment of TCP connections presents considerable overhead.

History[link]

Tim Berners-Lee

The term HyperText was coined by Ted Nelson who in turn was inspired by Vannevar Bush's microfilm-based "memex". Tim Berners-Lee first proposed the "WorldWideWeb" project — now known as the World Wide Web. Berners-Lee and his team are credited with inventing the original HTTP along with HTML and the associated technology for a web server and a text-based web browser. The first version of the protocol had only one method, namely GET, which would request a page from a server.^[3] The response from the server was always an HTML page.^[4]

The first documented version of HTTP was HTTP V0.9 (1991). Dave Raggett led the HTTP Working Group (HTTP WG) in 1995 and wanted to expand the protocol with extended operations, extended negotiation, richer meta-information, tied with a security protocol which became more efficient by adding additional methods and header fields.^[5][6] RFC 1945 officially introduced and recognized HTTP V1.0 in 1996.

The HTTP WG planned to publish new standards in December 1995^[7] and the support for pre-standard HTTP/1.1 based on the then developing RFC 2068 (called HTTP-NG) was rapidly adopted by the major browser developers in early 1996. By March 1996, pre-standard HTTP/1.1 was supported in Arena,^[8] Netscape 2.0,^[8] Netscape Navigator Gold 2.01,^[8] Mosaic 2.7,^{[citation needed]} Lynx 2.5^{[citation needed]}, and in Internet Explorer 2.0^{[citation needed]}. End-user adoption of the new browsers was rapid. In March 1996, one web hosting company reported that over 40% of browsers in use on the Internet were HTTP 1.1 compliant.^{[citation needed]} That same web hosting company reported that by June 1996, 65% of all browsers accessing their servers were HTTP/1.1 compliant.^[9] The HTTP/1.1 standard as defined in RFC 2068 was officially released in January 1997. Improvements and updates to the HTTP/1.1 standard were released under RFC 2616 in June 1999.

HTTP session[link]

An HTTP session is a sequence of network request-response transactions. An HTTP client initiates a request by establishing a Transmission Control Protocol (TCP) connection to a particular port on a server (typically port 80; see List of TCP and UDP port numbers). An HTTP server listening on that port waits for a client's request message. Upon receiving the request, the server sends back a status line, such as "HTTP/1.1 200 OK", and a message of its own. The body of this message is typically the requested resource, although an error message or other information may also be returned.^[1]

Request methods[link]

An HTTP request made using telnet. The request, response headers and response body are highlighted.

HTTP defines nine methods (sometimes referred to as "verbs") indicating the desired action to be performed on the identified resource. What this resource represents, whether pre-existing data or data that is generated dynamically, depends on the implementation of the server. Often, the resource corresponds to a file or the output of an executable residing on the server.

HEAD

Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content.

GET

Requests a representation of the specified resource. Requests using GET should only retrieve data and should have no other effect. (This is also true of some other HTTP methods.)^[1] The W3C has published guidance principles on this distinction, saying, "Web application design should be informed by the above principles, but also by the relevant limitations."^[10] See safe methods below.

POST

Submits data to be processed (e.g., from an HTML form) to the identified resource. The data is included in the body of the request. This may result in the creation of a new resource or the updates of existing resources or both.

PUT

Uploads a representation of the specified resource.

DELETE

Deletes the specified resource.

TRACE

Echoes back the received request, so that a client can see what (if any) changes or additions have been made by intermediate servers.

OPTIONS

Returns the HTTP methods that the server supports for specified URL. This can be used to check the functionality of a web server by requesting '*' instead of a specific resource.

CONNECT

Converts the request connection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy.^[11]

PATCH

Is used to apply partial modifications to a resource.^[12]

HTTP servers are required to implement at least the GET and HEAD methods^[13] and, whenever possible, also the OPTIONS method.^{[citation needed]}

Safe methods[link]

Some methods (for example, HEAD, GET, OPTIONS and TRACE) are defined as safe, which means they are intended only for information retrieval and should not change the state of the server. In other words, they should not have side effects, beyond relatively harmless effects such as logging, caching, the serving of banner advertisements or incrementing a web counter. Making arbitrary GET requests without regard to the context of the application's state should therefore be considered safe.

By contrast, methods such as POST, PUT and DELETE are intended for actions that may cause side effects either on the server, or external side effects such as financial transactions or transmission of email. Such methods are therefore not usually used by conforming web robots or web crawlers; some that do not conform tend to make requests without regard to context or consequences.

Despite the prescribed safety of GET requests, in practice their handling by the server is not technically limited in any way. Therefore, careless or deliberate programming can cause non-trivial changes on the server. This is discouraged, because it can cause problems for Web caching, search engines and other automated agents, which can make unintended changes on the server.

Idempotent methods and web applications[link]

Methods PUT and DELETE are defined to be idempotent, meaning that multiple identical requests should have the same effect as a single request (Note that idempotence refers to the state of the system after the request has completed, so while the action the server takes (e.g. deleting a record) or the response code it returns may be different on subsequent requests, the system state will be the same every time.) Methods GET, HEAD, OPTIONS and TRACE, being prescribed as safe, should also be idempotent, as HTTP is a stateless protocol.^[1]

In contrast, the POST method is not necessarily idempotent, and therefore sending an identical POST request multiple times may further affect state or cause further side effects (such as financial transactions). In some cases this may be desirable, but in other cases this could be due to an accident, such as when a user does not realize that their action will result in sending another request, or they did not receive adequate feedback that their first request was successful. While web browsers may show alert dialog boxes to warn users in some cases where reloading a page may re-submit a POST request, it is generally up to the web application to handle cases where a POST request should not be submitted more than once.

Note that whether a method is idempotent is not enforced by the protocol or web server. It is perfectly possible to write a web application in which (for example) a database insert or other non-idempotent action is triggered by a GET or other request. Ignoring this recommendation, however, may result in undesirable consequences, if a user agent assumes that repeating the same request is safe when it isn't.

Security[link]

Implementing methods such as TRACE, TRACK and DEBUG is considered potentially insecure by some security professionals, because they can be used by attackers to gather information or bypass security controls during attacks. Security software tools such as Tenable Nessus and Microsoft URLScan report on the presence of these methods as being security issues.

Status codes[link]

In HTTP/1.0 and since, the first line of the HTTP response is called the status line and includes a numeric status code (such as "404") and a textual reason phrase (such as "Not Found"). The way the user agent handles the response primarily depends on the code and secondarily on the response headers. Custom status codes can be used since, if the user agent encounters a code it does not recognize, it can use the first digit of the code to determine the general class of the response.^[14]

Also, the standard reason phrases are only recommendations and can be replaced with "local equivalents" at the web developer's discretion. If the status code indicated a problem, the user agent might display the reason phrase to the user to provide further information about the nature of the problem. The standard also allows the user agent to attempt to interpret the reason phrase, though this might be unwise since the standard explicitly specifies that status codes are machine-readable and reason phrases are human-readable.

Persistent connections[link]

In HTTP/0.9 and 1.0, the connection is closed after a single request/response pair. In HTTP/1.1 a keep-alive-mechanism was introduced, where a connection could be reused for more than one request. Such persistent connections reduce request latency perceptibly, because the client does not need to re-negotiate the TCP connection after the first request has been sent. Another positive side effect is that in general the connection becomes faster with time due to TCP's slow-start-mechanism.

Version 1.1 of the protocol also made bandwidth optimization improvements to HTTP/1.0. For example, HTTP/1.1 introduced chunked transfer encoding to allow content on persistent connections to be streamed rather than buffered. HTTP pipelining further reduces lag time, allowing clients to send multiple requests before waiting for each response. Another improvement to the protocol was byte serving, where a server transmits just the portion of a resource explicitly requested by a client.

HTTP session state[link]

HTTP is a stateless protocol. A stateless protocol does not require the server to retain information or status about each user for the duration of multiple requests. For example, when a web server is required to customize the content of a web page for a user, the web application may have to track the user's progress from page to page. A common solution is the use of HTTP cookies. Other methods include server side sessions, hidden variables (when the current page contains a form), and URL-rewriting using URI-encoded parameters, e.g., /index.php?session_id=some_unique_session_code.

Secure HTTP[link]

There are three methods of establishing a secure HTTP connection: HTTP Secure, Secure Hypertext Transfer Protocol and the HTTP/1.1 Upgrade header. Browser support for the latter two is, however, nearly non-existent,^{[citation needed]} so HTTP Secure is the dominant method of establishing a secure HTTP connection.

Request message[link]

The request message consists of the following:

• A request line, for example GET /images/logo.png HTTP/1.1, which requests a resource called /images/logo.png from the server.
• Headers, such as Accept-Language: en
• An empty line.
• An optional message body.

The request line and headers must all end with <CR><LF> (that is, a carriage return followed by a line feed). The empty line must consist of only <CR><LF> and no other whitespace.^[15] Although <CR><LF> is required <LF> alone is also accepted by most servers.^{[citation needed]} In the HTTP/1.1 protocol, all headers except Host are optional.

A request line containing only the path name is accepted by servers to maintain compatibility with HTTP clients before the HTTP/1.0 specification in RFC 1945.^[16]

Response message[link]

The response message consists of the following:

• A Status-Line (for example HTTP/1.1 200 OK, which indicates that the client's request succeeded)
• Headers, such as Content-Type: text/html
• An empty line
• An optional message body

The Status-Line and headers must all end with <CR><LF> (a carriage return followed by a line feed). The empty line must consist of only <CR><LF> and no other whitespace.^[17]

Example session[link]

Below is a sample conversation between an HTTP client and an HTTP server running on www.example.com, port 80.

Client request[link]

 GET /index.html HTTP/1.1␍␊
 Host: www.example.com␍␊
 ␍␊

A client request (consisting in this case of the request line and only one header) is followed by a blank line, so that the request ends with a double newline, each in the form of a carriage return followed by a line feed. The "Host" header distinguishes between various DNS names sharing a single IP address, allowing name-based virtual hosting. While optional in HTTP/1.0, it is mandatory in HTTP/1.1.

Server response[link]

 HTTP/1.1 200 OK
 Date: Mon, 23 May 2005 22:38:34 GMT
 Server: Apache/1.3.3.7 (Unix) (Red-Hat/Linux)
 Last-Modified: Wed, 08 Jan 2003 23:11:55 GMT
 Etag: "3f80f-1b6-3e1cb03b"
 Accept-Ranges:  none
 Content-Length: 438
 Connection: close
 Content-Type: text/html; charset=UTF-8

The ETag (entity tag) header is used to determine if a cached version of the requested resource is identical to the current version of the resource on the server. Content-Type specifies the Internet media type of the data conveyed by the HTTP message, while Content-Length indicates its length in bytes. The HTTP/1.1 webserver publishes its ability to respond to requests for certain byte ranges of the document by setting the header Accept-Ranges: bytes. This is useful, if the client needs to have only certain portions^[18] of a resource sent by the server, which is called byte serving. When Connection: close is sent in a header, it means that the web server will close the TCP connection immediately after the transfer of this response.

Most of the header lines are optional. When Content-Length is missing the length is determined in other ways. Chunked transfer encoding uses a chunk size of 0 to mark the end of the content. Identity encoding without Content-Length reads content until the socket is closed.

A Content-Encoding like gzip can be used to compress the transmitted data.

See also[link]

HTTP replacements or enhancements[link]

• Representational State Transfer (REST)
• SPDY - A HTTP enhancement proposed by Google
• Waka (protocol) - A HTTP replacement proposed by Roy Fielding
• HTTP-MPLEX - A backwards compatible enhancement to HTTP to improve page and web object retrieval time in congested networks proposed by Robert Mattson
• HTTP 2.0 - currently being worked on by the IETF's Hypertext Transfer Protocol Bis (httpbis) working group.^[19]
• Constrained Application Protocol - A semantically similar protocol to HTTP but used UDP or UDP-like messages targeted for devices with limited processing capability. Re-uses HTTP and other internet concepts like Internet media type and web linking (http://tools.ietf.org/html/rfc5988).

Further Information[link]

• Basic access authentication
• Content negotiation
• HTTP compression
• Hxxp

Related topics and technologies[link]

• Curl-loader - HTTP/S loading/testing open-source SW
• Digest access authentication
• List of file transfer protocols
• List of HTTP headers
• List of HTTP status codes
• Web cache
• WebDAV

References[link]

Further reading[link]

• HTTP 0.9 - As Implemented in 1991

External links[link]

Wikimedia Commons has media related to: HTTP

• "Change History for HTTP". W3.org. http://www.w3.org/Protocols/History.html. Retrieved 2010-08-01.  A detailed technical history of HTTP.
• "Design Issues for HTTP". W3.org. http://www.w3.org/Protocols/DesignIssues.html. Retrieved 2010-08-01.  Design Issues by Berners-Lee when he was designing the protocol.
• "Classic HTTP Documents". W3.org. 1998-05-14. http://www.w3.org/Protocols/Classic.html. Retrieved 2010-08-01.  list of other classic documents recounting the early protocol history

Steve Jobs
Jobs holding a white iPhone 4 at Worldwide Developers Conference 2010
Born	Steven Paul Jobs (1955-02-24)February 24, 1955[1][2] San Francisco, California, U.S.[1][2]
Died	October 5, 2011(2011-10-05) (aged 56)[2] Palo Alto, California, U.S.
Cause of death	Pancreatic cancer
Nationality	American
Ethnicity	Syrian, German[3]
Alma mater	Reed College (dropped out)
Occupation	Co-founder, Chairman and CEO, Apple Inc. Co-founder and CEO, Pixar Co-founder and CEO, NeXT Inc.
Years active	1974–2011
Board member of	The Walt Disney Company[4] Apple Inc.
Religion	Zen Buddhism
Spouse	Laurene Powell (1991–2011, his death)
Children	Lisa Brennan-Jobs Reed Erin Eve
Relatives	Mona Simpson (sister)
Signature

Steven Paul "Steve" Jobs (/ˈdʒɒbz/; February 24, 1955 – October 5, 2011)^[5][6] was an American businessman, designer and inventor. He is best known as the co-founder, chairman, and chief executive officer of Apple Inc. Through Apple, he was widely recognized as a charismatic pioneer of the personal computer revolution^[7][8] and for his influential career in the computer and consumer electronics fields. Jobs also co-founded and served as chief executive of Pixar Animation Studios; he became a member of the board of directors of The Walt Disney Company in 2006, when Disney acquired Pixar.

In the late 1970s, Apple co-founder Steve Wozniak engineered one of the first commercially successful lines of personal computers, the Apple II series. Jobs was among the first to see the commercial potential of Xerox PARC's mouse-driven graphical user interface, which led to the creation of the Apple Lisa and, one year later, the Macintosh. During this period he also led efforts that would begin the desktop publishing revolution, notably through the introduction of the LaserWriter and the associated PageMaker software.^[9]

After losing a power struggle with the board of directors in 1985, Jobs left Apple and founded NeXT, a computer platform development company specializing in the higher-education and business markets. In 1986, he acquired the computer graphics division of Lucasfilm, which was spun off as Pixar.^[10] He was credited in Toy Story (1995) as an executive producer. He remained CEO and majority shareholder at 50.1 percent until its acquisition by The Walt Disney Company in 2006,^[11] making Jobs Disney's largest individual shareholder at seven percent and a member of Disney's Board of Directors.^[12][13]

After difficulties developing a new Mac operating system, Apple purchased NeXT in 1996 in order to use NeXTSTEP as the basis for what became Mac OS X.^[14] As part of the deal Jobs was named Apple advisor. As Apple floundered, Jobs took control of the company and was named "interim CEO" in 1997, or as he jokingly referred to it, "iCEO". Under his leadership, Apple was saved from near bankruptcy, and became profitable by 1998.^[15][16] Over the next decade, Jobs oversaw the development of the iMac, iTunes, iPod, iPhone, and iPad, and on the services side, the company's Apple Retail Stores, iTunes Store and the App Store.^[17] The success of these products and services, providing several years of stable financial returns, propelled Apple to become the world's most valuable publicly traded company in 2011.^[18] The reinvigoration of the company is regarded by many commentators as one of the greatest turnarounds in business history.^[19][20][21]

In 2003, Jobs was diagnosed with a pancreas neuroendocrine tumor. Though it was initially treated, he reported a hormone imbalance, underwent a liver transplant in 2009, and appeared progressively thinner as his health declined.^[22] On medical leave for most of 2011, Jobs resigned as Apple CEO in August that year and was elected Chairman of the Board. He died of respiratory arrest related to his metastatic tumor on October 5, 2011.

Jobs has received a number of honors and public recognition for his influence in the technology and music industries. He has widely been referred to as "legendary", a "futurist" or simply "visionary",^{[23][24][25][26]} and has been described as the "Father of the Digital Revolution",^[27] a "master of innovation",^[28][29] and a "design perfectionist".^[30][31]

Early life and education[link]

Steven Paul Jobs was born in San Francisco on February 24, 1955 to two university students, Joanne Carole Schieble and Syrian-born Abdulfattah "John" Jandali (Arabic: عبدالفتاح جندلي‎), who were both unmarried at the time.^[32] Jandali, who was teaching in Wisconsin when Steve was born in 1955, said he had no choice but to put the baby up for adoption because his girlfriend's family objected to their relationship.^[33] The baby was adopted at birth by Paul Reinhold Jobs (1922–1993) and Clara Jobs (1924–1986), an Armenian-American^[3] whose maiden name was Hagopian.^[34] Later, when asked about his "adoptive parents," Jobs replied emphatically that Paul and Clara Jobs "were my parents."^[35] He stated in his authorized biography that they "were my parents 1,000%."^[36] Unknown to him, his biological parents would subsequently marry (December 1955), have a second child Mona Simpson in 1957, and divorce in 1962.^[36]

The Jobs family moved from San Francisco to Mountain View, California when Steve was five years old.^[1][2] The parents later adopted a daughter, Patti. Paul was a machinist for a company that made lasers, and taught his son rudimentary electronics and how to work with his hands.^[1] The father showed Steve how to work on electronics in the family garage, demonstrating to his son how to take apart and rebuild electronics such as radios and televisions. As a result, Steve became interested in and developed a hobby of technical tinkering.^[37]

Clara was an accountant^[35] who taught him to read before he went to school.^[1] Clara Jobs had been a payroll clerk for Varian Associates, one of the first high-tech firms in what became known as Silicon Valley.^[38]

Jobs's youth was riddled with frustrations over formal schooling. At Monta Loma Elementary school in Mountain View, he was a prankster whose fourth-grade teacher needed to bribe him to study. Jobs tested so well, however, that administrators wanted to skip him ahead to high school—a proposal his parents declined.^[39]

Jobs then attended Cupertino Junior High and Homestead High School in Cupertino, California.^[2] At Homestead, Jobs became friends with Bill Fernandez, a neighbor who shared the same interests in electronics. Fernandez introduced Jobs to another, older computer whiz kid, Stephen Wozniak (also known as "Woz"). In 1969 Woz started building a little computer board with Fernandez that they named “The Cream Soda Computer”, which they showed to Jobs; he seemed really interested.^[40] Jobs frequented after-school lectures at the Hewlett-Packard Company in Palo Alto, California, and was later hired there, working with Wozniak as a summer employee.^[41]

Following high school graduation in 1972, Jobs enrolled at Reed College in Portland, Oregon. Reed was an expensive college which Paul and Clara could ill afford. They were spending much of their life savings on their son’s higher education.^[40] Jobs dropped out of college after six months and spent the next 18 months dropping in on creative classes, including a course on calligraphy.^[42] He continued auditing classes at Reed while sleeping on the floor in friends' dorm rooms, returning Coke bottles for food money, and getting weekly free meals at the local Hare Krishna temple.^[43] Jobs later said, "If I had never dropped in on that single calligraphy course in college, the Mac would have never had multiple typefaces or proportionally spaced fonts."^[43]

Early career[link]

This section may be in need of reorganization to comply with Wikipedia's layout guidelines. Please help by editing the article to make improvements to the overall structure. (March 2012)

Homebrew Computer Club Newsletter, September 1976

In 1974, Jobs took a job as a technician at Atari, Inc. in Los Gatos, California.^[44] He traveled to India in mid-1974^[45] to visit Neem Karoli Baba^[46] at his Kainchi Ashram with a Reed College friend (and, later, an early Apple employee), Daniel Kottke, in search of spiritual enlightenment. When they got to the Neem Karoli ashram, it was almost deserted as Neem Karoli Baba had died in September 1973.^[44] Then they made a long trek up a dry riverbed to an ashram of Hariakhan Baba. In India, they spent a lot of time on bus rides from Delhi to Uttar Pradesh and back, then up to Himachal Pradesh and back.^[44]

After staying for seven months, Jobs left India^[47] and returned to the US ahead of Daniel Kottke.^[44] Jobs had changed his appearance; his head was shaved and he wore traditional Indian clothing.^[48][49] During this time, Jobs experimented with psychedelics, later calling his LSD experiences "one of the two or three most important things [he had] done in [his] life".^[50] He also became a serious practitioner of Zen Buddhism, engaged in lengthy meditation retreats at the Tassajara Zen Mountain Center, the oldest Sōtō Zen monastery in the US.^[51] He considered taking up monastic residence at Eihei-ji in Japan, and maintained a lifelong appreciation for Zen.^[52] Jobs would later say that people around him who did not share his countercultural roots could not fully relate to his thinking.^[50]

Jobs then returned to Atari, and was assigned to create a circuit board for the arcade video game Breakout. According to Atari co-founder Nolan Bushnell, Atari offered $100 for each chip that was eliminated in the machine. At that time, Jobs had little specialized knowledge of circuit board design and made a deal with Wozniak to split the fee evenly between them if Wozniak could minimize the number of chips. Much to the amazement of Atari engineers, Wozniak reduced the number of chips by 50, a design so tight that it was impossible to reproduce on an assembly line.^{[further explanation needed]} According to Wozniak, Jobs told him that Atari gave them only $700 (instead of the offered $5,000), and that Wozniak's share was thus $350.^[53] Wozniak did not learn about the actual bonus until ten years later, but said that if Jobs had told him about it and had said he needed the money, Wozniak would have given it to him.^[54]

In the early 1970s, Jobs and Wozniak were drawn to technology like a magnet. Wozniak had designed a low-cost digital "blue box" to generate the necessary tones to manipulate the telephone network, allowing free long-distance calls. Jobs decided that they could make money selling it. The clandestine sales of the illegal "blue boxes" went well, and perhaps planted the seed in Jobs's mind that electronics could be fun and profitable.^[55]

In 1976, Jobs and Wozniak formed their own business, which they named “Apple Computer Company” in remembrance of a happy summer Jobs had spent picking apples. At first they started off selling circuit boards, but eventually they produced a complete computer prototype.^[56] Jobs began attending meetings of the Homebrew Computer Club with Wozniak in 1975.^[2] He greatly admired Edwin H. Land, the inventor of instant photography and founder of Polaroid Corporation, and would explicitly model his own career after that of Land's.^[57][58]

Career[link]

Apple Computer[link]

Home of Paul and Clara Jobs, on Crist Drive in Los Altos, California. Steve Jobs formed Apple Computer in its garage with Steve Wozniak and Ronald Wayne in 1976. Wayne stayed only a short time, leaving Jobs and Wozniak as the primary co-founders of the company.

Jobs and Steve Wozniak met in 1971, when their mutual friend, Bill Fernandez, introduced 21-year-old Wozniak to 16-year-old Jobs. In 1976, Wozniak invented the Apple I computer. Jobs, Wozniak, and Ronald Wayne founded Apple computer in the garage of Jobs's parents in order to sell it.^[59] They received funding from a then-semi-retired Intel product-marketing manager and engineer Mike Markkula.^[60]

In 1978, Apple recruited Mike Scott from National Semiconductor to serve as CEO for what turned out to be several turbulent years. In 1983, Jobs lured John Sculley away from Pepsi-Cola to serve as Apple's CEO, asking, "Do you want to sell sugar water for the rest of your life, or do you want to come with me and change the world?"^[61]

In the early 1980s, Jobs was among the first to see the commercial potential of Xerox PARC's mouse-driven graphical user interface, which led to the creation of the Apple Lisa. One year later, Apple employee Jef Raskin invented the Macintosh.^[62][63]

The following year, Apple aired a Super Bowl television commercial titled "1984". At Apple's annual shareholders meeting on January 24, 1984, an emotional Jobs introduced the Macintosh to a wildly enthusiastic audience; Andy Hertzfeld described the scene as "pandemonium".^[64]

Apple logo in 1977, created by Rob Janoff with the rainbow color theme used until 1998.

While Jobs was a persuasive and charismatic director for Apple, some of his employees from that time described him as an erratic and temperamental manager. Disappointing sales caused a deterioration in Jobs's working relationship with Sculley and it eventually became a power struggle between Jobs and Sculley.^[65] Jobs kept meetings running past midnight, sent out lengthy faxes, then called new meetings at 7:00 am.^[66]

Sculley learned that Jobs—believing Sculley to be "bad for Apple" and the wrong person to lead the company—had been attempting to organize a boardroom coup, and on May 24, 1985, called a board meeting to resolve the matter.^[65] Apple's board of directors sided with Sculley and removed Jobs from his managerial duties as head of the Macintosh division.^[67][68] Jobs resigned from Apple five months later^[65] and founded NeXT Inc. the same year.^[66][69]

In a speech Jobs gave at Stanford University in 2005, he said being fired from Apple was the best thing that could have happened to him; "The heaviness of being successful was replaced by the lightness of being a beginner again, less sure about everything. It freed me to enter one of the most creative periods of my life." And he added, "I'm pretty sure none of this would have happened if I hadn't been fired from Apple. It was awful-tasting medicine, but I guess the patient needed it."^[43][70][71]

NeXT Computer[link]

A NeXTstation with the original keyboard, mouse and the NeXT MegaPixel monitor

After leaving Apple, Jobs founded NeXT Computer in 1985, with $7 million. A year later, Jobs was running out of money, and with no product on the horizon, he appealed for venture capital. Eventually, he attracted the attention of billionaire Ross Perot who invested heavily in the company.^[72] NeXT workstations were first released in 1990, priced at $9,999. Like the Apple Lisa, the NeXT workstation was technologically advanced, but was largely dismissed as cost-prohibitive by the educational sector for which it was designed.^[73] The NeXT workstation was known for its technical strengths, chief among them its object-oriented software development system. Jobs marketed NeXT products to the financial, scientific, and academic community, highlighting its innovative, experimental new technologies, such as the Mach kernel, the digital signal processor chip, and the built-in Ethernet port. Tim Berners-Lee invented the World Wide Web on a NeXT computer at CERN.^[74]

The revised, second-generation NeXTcube was released in 1990, also. Jobs touted it as the first "interpersonal" computer that would replace the personal computer. With its innovative NeXTMail multimedia email system, NeXTcube could share voice, image, graphics, and video in email for the first time. "Interpersonal computing is going to revolutionize human communications and groupwork", Jobs told reporters.^[75] Jobs ran NeXT with an obsession for aesthetic perfection, as evidenced by the development of and attention to NeXTcube's magnesium case.^[76] This put considerable strain on NeXT's hardware division, and in 1993, after having sold only 50,000 machines, NeXT transitioned fully to software development with the release of NeXTSTEP/Intel.^[77] The company reported its first profit of $1.03 million in 1994.^[72] In 1996, NeXT Software, Inc. released WebObjects, a framework for Web application development. After NeXT was acquired by Apple Inc. in 1997, WebObjects was used to build and run the Apple Store,^[77] MobileMe services, and the iTunes Store.

Pixar and Disney[link]

In 1986, Jobs bought The Graphics Group (later renamed Pixar) from Lucasfilm's computer graphics division for the price of $10 million, $5 million of which was given to the company as capital.^[78]

The first film produced by the partnership, Toy Story, with Jobs credited as executive producer,^[79] brought fame and critical acclaim to the studio when it was released in 1995. Over the next 15 years, under Pixar's creative chief John Lasseter, the company produced box-office hits A Bug's Life (1998); Toy Story 2 (1999); Monsters, Inc. (2001); Finding Nemo (2003); The Incredibles (2004); Cars (2006); Ratatouille (2007); WALL-E (2008); Up (2009); and Toy Story 3 (2010). Finding Nemo, The Incredibles, Ratatouille, WALL-E, Up and Toy Story 3 each received the Academy Award for Best Animated Feature, an award introduced in 2001.^[80]

Steve Jobs on computer graphics Steve Jobs on computer graphics. Interview excerpt from 1995.[81]

In the years 2003 and 2004, as Pixar's contract with Disney was running out, Jobs and Disney chief executive Michael Eisner tried but failed to negotiate a new partnership,^[82] and in early 2004, Jobs announced that Pixar would seek a new partner to distribute its films after its contract with Disney expired.

In October 2005, Bob Iger replaced Eisner at Disney, and Iger quickly worked to patch up relations with Jobs and Pixar. On January 24, 2006, Jobs and Iger announced that Disney had agreed to purchase Pixar in an all-stock transaction worth $7.4 billion. When the deal closed, Jobs became The Walt Disney Company's largest single shareholder with approximately seven percent of the company's stock.^[12] Jobs's holdings in Disney far exceeded those of Eisner, who holds 1.7 percent, and of Disney family member Roy E. Disney, who until his 2009 death held about one percent of the company's stock and whose criticisms of Eisner — especially that he soured Disney's relationship with Pixar — accelerated Eisner's ousting. Jobs joined the company's board of directors upon completion of the merger and also helped oversee Disney and Pixar's combined animation businesses from a seat on a special six-person steering committee.^[83] Upon Jobs's death his shares in Disney were transferred to the Steven P. Jobs Trust led by Laurene Jobs.^[84]

Return to Apple[link]

Logo for the Think Different campaign designed by TBWA\Chiat\Day and initiated by Jobs after his return to Apple Computer in 1997.

In 1996, Apple announced that it would buy NeXT for $427 million. The deal was finalized in late 1996,^[85] bringing Jobs back to the company he co-founded. Jobs became de facto chief after then-CEO Gil Amelio was ousted in July 1997. He was formally named interim chief executive in September.^[86] In March 1998, to concentrate Apple's efforts on returning to profitability, Jobs terminated a number of projects, such as Newton, Cyberdog, and OpenDoc. In the coming months, many employees developed a fear of encountering Jobs while riding in the elevator, "afraid that they might not have a job when the doors opened. The reality was that Jobs's summary executions were rare, but a handful of victims was enough to terrorize a whole company."^[87] Jobs also changed the licensing program for Macintosh clones, making it too costly for the manufacturers to continue making machines.