Meta tags:
Headings (most frequently used words):
the, rest, contents, history, meaning, of, name, six, constraints, that, formally, define, implied, architectural, properties, classification, models, see, also, references, further, reading, uniform, interface,
Text of the page (most frequently used words):
the (140), web (47), and (44), rest (43), search (32), architectural (27), for (23), server (21), client (21), that (18), with (17), from (17), #constraints (16), based (14), are (14), retrieved (13), software (12), fielding (12), design (12), architecture (11), network (11), engine (10), application (10), resource (10), http (10), original (10), archived (10), style (10), apis (9), interface (9), which (9), can (9), wikipedia (8), page (8), was (8), information (8), state (8), roy (8), styles (8), system (8), uniform (8), six (8), this (7), transfer (7), standards (7), restful (7), applications (7), such (7), components (7), url (6), other (6), see (6), also (6), service (6), api (6), data (6), isbn (6), services (6), 2000 (6), architectures (6), properties (6), view (5), protocol (5), classification (5), oriented (5), internet (5), com (5), model (5), thomas (5), california (5), irvine (5), scalability (5), resources (5), languages (4), contents (4), code (4), text (4), available (4), may (4), using (4), use (4), description (4), wide (4), representational (4), tools (4), semantic (4), topics (4), scripting (4), maturity (4), world (4), 2024 (4), 2023 (4), university (4), chapter (4), media (4), pattern (4), uri (4), content (4), their (4), performance (4), links (4), need (4), when (4), identified (4), defined (4), formally (4), these (4), define (4), they (4), create (4), history (4), hide (4), move (4), sidebar (4), toggle (3), privacy (3), international (3), via (3), protocols (3), website (3), standard (3), cross (3), language (3), security (3), browser (3), file (3), richardson (3), 978 (3), pautasso (3), cesare (3), 2008 (3), conference (3), 2014 (3), 2015 (3), what (3), term (3), between (3), computer (3), identifier (3), models (3), been (3), within (3), needs (3), while (3), large (3), user (3), together (3), requirements (3), but (3), more (3), scale (3), implied (3), hypermedia (3), there (3), example (3), representation (3), any (3), html (3), stateless (3), formal (3), means (3), implementation (3), created (3), become (3), changes (3), main (3), table (2), developers (2), contact (2), about (2), policy (2), terms (2), apply (2), site (2), agree (2), non (2), categories (2), cs1 (2), maint (2), status (2), pages (2), short (2), wikidata (2), hypertext (2), index (2), retrieve (2), query (2), distributed (2), crawler (2), document (2), retrieval (2), evaluation (2), human (2), enterprise (2), video (2), audio (2), social (2), list (2), microservices (2), related (2), discontinued (2), database (2), dom (2), events (2), w3c (2), storage (2), side (2), container (2), ruby (2), python (2), asp (2), net (2), 2010 (2), 2017 (2), frank (2), april (2), further (2), reading (2), june (2), new (2), link (2), cite (2), 2019 (2), hateoas (2), 2012 (2), principles (2), groups (2), 2021 (2), must (2), references (2), descriptions (2), loosely (2), coupled (2), used (2), several (2), help (2), reliability (2), portability (2), visibility (2), communication (2), modifiability (2), even (2), extensibility (2), simplicity (2), support (2), interactions (2), affect (2), following (2), provided (2), independent (2), low (2), entry (2), barrier (2), designed (2), specifically (2), adoption (2), having (2), should (2), able (2), all (2), responds (2), includes (2), time (2), regarding (2), each (2), message (2), enough (2), parser (2), representations (2), has (2), requests (2), its (2), uris (2), constraint (2), part (2), servers (2), demand (2), layered (2), cache (2), specific (2), does (2), not (2), set (2), desirable (2), change (2), only (2), identifiers (2), those (2), meaning (2), name (2), development (2), shared (2), caching (2), creating (2), existing (2), features (2), concept (2), considered (2), started (2), community (2), extensions (2), general (2), legacy (2), appearance (2), upload (2), source (2), read (2), english (2), article (2), edit (2), log (2), account (2), donate (2), menu (2), add, topic, mobile, cookie, statement, statistics, conduct, legal, safety, contacts, disclaimers, under, additional, you, registered, trademark, profit, organization, wikimedia, foundation, inc, creative, commons, attribution, sharealike, license, rendered, parsoid, last, edited, september, 2026, utc, hidden, indefinitely, semi, protected, different, articles, neologisms, cloud, https, org, php, title, oldid, 1377040586, yale, lux, israel, united, states, national, fast, gnd, authority, control, databases, online, desktop, area, opensearch, z39, mirroring, archiving, crawling, robots, exclusion, spider, trap, focused, indexing, aggregator, federated, multisearch, mining, selection, measures, optimization, marketing, sound, contextual, searching, flesh, voice, natural, algorithm, image, vertical, local, collaborative, multimedia, metasearch, types, framework, progressive, single, rich, dynamic, static, solution, stack, push, technology, graphql, frontend, backend, idl, persistent, mashup, hydration, cors, extension, dhtml, remote, ajax, webusb, sql, gears, others, webgl, webcl, khronos, webxr, webrtc, webgpu, webauthn, webassembly, svg, mse, indexeddb, geolocation, eme, xmlhttprequest, worker, messaging, websockets, sse, canvas, whatwg, xbap, bho, activex, nacl, ppapi, npruntime, xpconnect, liveconnect, npapi, comparison, webhook, open, roa, woa, phusion, passenger, mod_ruby, mod_wsgi, mod_python, mod_proxy, mod_php, mod_perl, mod_parrot, mod_mono, mod_lisp, mod_jk, mod_include, apache, modules, portlet, perl, psgi, javascript, jsgi, rack, asgi, wsgi, handler, cli, owin, jakarta, servlet, isapi, asapi, nsapi, websocket, wsrp, ajp, fcgi, scgi, cgi, webdav, encryption, interfaces, fowler, martin, martinfowler, steps, towards, glory, ferreira, otavio, nov, 2009, iadis, 972, 8924, approach, zimmermann, olaf, leymann, big, 814, 207167438, s2cid, 9781605580852, 1145, 1367497, 1367606, doi, 805, proceedings, 17th, wilde, erik, alarcon, rosa, springer, 9781461492986, advanced, research, practical, ivan, salvadori, siqueira, york, researchgate, 2020, icws, ieee, onat, algermissen, thesis, 2025, designing, problems, insights, gupta, lokesh, 2018, restfulapi, march, tutorial, www, visual, paradigm, leonard, sam, 2007, sebastopol, reilly, 596, 52926, erl, carlyle, benjamin, balasubramanian, raj, upper, saddle, river, jersey, prentice, hall, 701251, soa, patterns, building, solutions, yahoo, november, discussing, definition, experience, couldry, nick, london, polity, press, 9780745639208, society, theory, digital, practice, gbiv, 2016, driven, 2004, offered, electronic, devices, computing, overview, collection, build, namespace, assigned, iana, schemes, dap, domain, ecosystem, layer, addresses, bottlenecks, delivery, intended, improve, usability, clean, have, developed, classify, according, adherence, various, resistance, failure, level, presence, failures, connectors, moving, program, agents, meet, changing, running, allowing, numbers, among, component, dominant, factor, perceived, efficiency, concepts, expressed, entity, relationship, decoupling, addressing, basis, meeting, anarchic, deployment, grain, readers, authors, than, usage, coupling, possible, facilitate, loose, origin, agent, accessed, initial, analogous, accessing, then, dynamically, discover, access, proceeds, response, hard, coded, structure, hyperlinks, home, self, descriptive, messages, describe, how, process, invoke, specified, type, manipulation, through, holds, including, attached, modify, delete, metadata, identification, individual, themselves, conceptually, separate, returned, could, send, none, internal, json, xml, fundamental, simplifies, decouples, enables, evolve, independently, four, optional, temporarily, extend, customize, functionality, transferring, logic, executed, virtual, machine, cannot, ordinarily, tell, whether, connected, directly, end, intermediary, along, way, responses, indicate, own, cacheability, consume, clients, separated, well, follows, guiding, implications, gains, functional, upon, receiving, request, will, respond, usually, contains, followed, make, known, first, requested, discovered, allows, without, inform, beforehand, thus, inherently, nature, obey, every, mismatches, occur, due, ignorance, oversight, existence, before, standardised, embedding, session, violation, negatively, violate, because, out, sync, making, them, unreliable, contain, opaque, concern, cookies, enable, global, surveyed, many, identifying, unique, trying, both, categorise, identify, aspects, central, behavioural, work, three, primary, scientist, involved, creation, during, next, years, testing, improvements, his, phd, dissertation, working, ietf, began, enter, everyday, 1993, 1994, fragmented, existed, pressure, instance, experimental, had, added, were, being, proposed, evaluate, impact, proxies, websites, speaking, oscon, reliable, adheres, informally, described, although, commonly, associated, widely, best, practices, commands, little, originally, formulated, often, odds, methods, motivation, grant, compatibility, systems, latency, reduction, modularity, ideal, below, guide, uses, disambiguation, redirected, free, encyclopedia, item, projects, printable, version, download, pdf, print, export, switch, get, shortened, permanent, here, actions, talk, اردو, українська, türkçe, ไทย, svenska, simple, русский, runa, simi, português, polski, norsk, bokmål, nederlands, 한국어, qaraqalpaqsha, 日本語, italiano, bahasa, indonesia, magyar, עברית, français, suomi, فارسی, euskara, eesti, español, deutsch, dansk, čeština, català, български, azərbaycanca, العربية, subsection, top, personal, special, recent, portal, learn, contribute, random, current, navigation, jump,
Text of the page (random words):
eesti euskara فارسی suomi français עברית magyar bahasa indonesia italiano 日本語 qaraqalpaqsha 한국어 nederlands norsk bokmål polski português runa simi русский simple english svenska ไทย türkçe українська اردو 中文 edit links article talk english read view source view history tools tools move to sidebar hide actions read view source view history general what links here related changes upload file permanent link page information cite this page get shortened url switch to legacy parser print export download as pdf printable version in other projects wikidata item appearance move to sidebar hide from wikipedia the free encyclopedia redirected from rest api architectural style for client server applications for other uses see rest disambiguation rest representational state transfer is a software architectural style that was created in 2000 to guide the development of the world wide web rest is defined as a set of six constraints for the ideal architecture of a distributed internet scale hypermedia system such as the web client server stateless cache uniform interface layered system and code on demand see the six constraints below the motivation for these six constraints is to grant the system desirable properties such as modularity scalability latency reduction security and compatibility with legacy systems see implied architectural properties 1 rest has been used to create stateless reliable web based applications an application that adheres to the rest architectural constraints may be informally described as restful although this term is more commonly associated with the design of http based apis and what are widely considered best practices regarding the commands http methods a resource responds to while having little to do with rest as originally formulated and is often even at odds with the concept 2 history roy fielding speaking at oscon 2008 the web began to enter everyday use in 1993 1994 when websites for general use started to become available 3 at the time only a fragmented description existed of the web s architecture and there was pressure within the community to agree on a standard for the web interface protocols for instance several experimental extensions had been added to the communication protocol http to support proxies and more extensions were being proposed but there was a need for a formal web architecture with which to evaluate the impact of these changes 4 the w3c and ietf working groups together started work on creating formal descriptions of the web s three primary standards uri http and html the computer scientist roy fielding was involved in the creation of these standards specifically http 1 0 and 1 1 and uri and during the next six years he created the rest architectural style testing its constraints on the web s protocol standards and using it as a means to define architectural improvements fielding defined rest in his 2000 phd dissertation architectural styles and the design of network based software architectures 1 5 at uc irvine to create the rest architectural style fielding identified the requirements that apply when creating a world wide network based application such as the need for a low entry barrier to enable global adoption he also surveyed many existing architectural styles for network based applications identifying which features are shared with other styles such as caching and client server features and those which are unique to rest such as the concept of resources fielding was trying to both categorise the architecture of the existing implementation and identify which aspects should be considered central to the behavioural and performance requirements of the web by their nature architectural styles are independent of any specific implementation and while rest was created as part of the development of the web standards the implementation of the web does not obey every constraint in the rest architectural style mismatches can occur due to ignorance or oversight but the existence of the rest architectural style means that they can be identified before they become standardised for example fielding identified the embedding of session information in uris as a violation of the constraints of rest which can negatively affect shared caching and server scalability http cookies also violate rest constraints 4 because they can become out of sync with the browser s application state making them unreliable they also contain opaque data that can be a concern for privacy and security the meaning of the name the term representational state transfer means that upon receiving a client request a server will respond with the representation of a resource usually an html document that contains hypermedia links that can be followed to make the state of the system change the only identifier that needs to be known to the client is the identifier of the first resource requested and all other identifiers may be discovered this allows those identifiers to change without the need to inform the client beforehand thus the client and server are inherently loosely coupled the six constraints that formally define rest the rest architectural style may be formally defined as a set of six guiding constraints together with their implications 6 7 a system following these constraints gains desirable non functional properties such as performance scalability simplicity modifiability visibility portability and reliability 1 the formal rest constraints are as follows 8 client server clients are separated from servers by a well defined interface stateless a specific client does not consume server storage when the client is at rest cache responses indicate their own cacheability uniform interface layered system a client cannot ordinarily tell whether it is connected directly to the end server or to an intermediary along the way code on demand optional servers are able to temporarily extend or customize the functionality of a client by transferring logic to the client that can be executed within a standard virtual machine uniform interface the uniform interface constraint is fundamental to the design of any restful system 1 it simplifies and decouples the architecture which enables each part to evolve independently the four constraints for this uniform interface are resource identification in requests individual resources are identified in requests using uris the resources themselves are conceptually separate from the representations that are returned to the client for example the server could send data from its database as html xml or as json none of which are the server s internal representation resource manipulation through representations when a client holds a representation of a resource including any metadata attached it has enough information to modify or delete the resource s state self descriptive messages each message includes enough information to describe how to process the message for example which parser to invoke can be specified by a media type 1 hypermedia as the engine of application state hateoas having accessed an initial uri for the rest application analogous to a human web user accessing the home page of a website a rest client should then be able to use server provided links dynamically to discover all the available resources it needs as access proceeds the server responds with text that includes hyperlinks to other resources that are available at the time of the response there is no need for the client to be hard coded with information regarding the structure of the server 9 implied architectural properties the rest architectural style is designed for network based applications specifically client server applications but more than that it is designed for internet scale usage so the coupling between the user agent client and the origin server must be as loose as possible to facilitate large scale adoption this decoupling of client and server together with the text based transfer of information using a uniform addressing protocol provided the basis for meeting the requirements of the web extensibility anarchic scalability 10 and independent deployment of components large grain data transfer and a low entry barrier for content readers content authors and developers an entity relationship model of the concepts expressed in the rest architectural style the constraints of the rest architectural style affect the following architectural properties 1 6 performance in component interactions which can be the dominant factor in user perceived performance and network efficiency 11 scalability allowing the support of large numbers of components and interactions among components simplicity of a uniform interface modifiability a k a extensibility of components to meet changing needs even while the application is running visibility of communication between components by service agents portability of components by moving program code with the data reliability in the resistance to failure at the system level in the presence of failures within components connectors or data 11 classification models several models have been developed to help classify http apis according to their adherence to various principles of rest design such as the richardson maturity model the classification of http based apis 12 the w s 3 maturity model 13 see also clean url url intended to improve the usability of a website content delivery network internet ecosystem layer that addresses bottlenecks domain application protocol dap list of uri schemes namespace identifier assigned by iana microservices collection of loosely coupled services used to build computer applications overview of restful api description languages descriptions of computer languages resource oriented architecture architectural pattern in software design resource oriented computing architectural pattern in software design service oriented architecture architectural pattern in software design web oriented architecture architectural pattern in software design web service service offered between electronic devices via the internet references 1 2 3 4 5 6 fielding roy thomas 2000 chapter 5 representational state transfer rest architectural styles and the design of network based software architectures ph d university of california irvine archived from the original on 2021 05 13 retrieved 2004 08 17 fielding roy t 2008 10 20 rest apis must be hypertext driven roy gbiv com archived from the original on 2010 03 18 retrieved 2016 07 06 couldry nick 2012 media society world social theory and digital media practice london polity press p 2 isbn 9780745639208 archived from the original on 2024 02 27 retrieved 2021 06 09 1 2 fielding roy thomas 2000 chapter 6 experience and evaluation architectural styles and the design of network based software architectures ph d university of california irvine archived from the original on 2023 03 26 retrieved 2023 06 21 fielding discussing the definition of the rest term groups yahoo com archived from the original on november 5 2015 retrieved 2017 08 08 1 2 erl thomas carlyle benjamin pautasso cesare balasubramanian raj 2012 5 1 soa with rest principles patterns constraints for building enterprise solutions with rest upper saddle river new jersey prentice hall isbn 978 0 13 701251 0 richardson leonard ruby sam 2007 restful web services sebastopol california o reilly media isbn 978 0 596 52926 0 what is rest api www visual paradigm com archived from the original on 2024 02 24 retrieved 2024 02 24 gupta lokesh 2 june 2018 rest hateoas rest api tutorial restfulapi net archived from the original on 7 april 2019 retrieved march 10 2019 fielding roy thomas 2000 chapter 4 designing the web architecture problems and insights architectural styles and the design of network based software architectures ph d university of california irvine retrieved 2025 01 28 cite thesis cs1 maint url status link 1 2 fielding roy thomas 2000 chapter 2 network based application architectures architectural styles and the design of network based software architectures ph d university of california irvine archived from the original on 2014 12 16 retrieved 2014 04 12 classification of http apis algermissen io archived from the original on 2023 01 29 retrieved 2023 01 29 ivan salvadori frank siqueira june 2015 a maturity model for semantic restful web apis conference web services icws 2015 ieee international conference onat new york archived from the original on 2024 02 27 retrieved 2020 12 14 via researchgate further reading pautasso cesare wilde erik alarcon rosa 2014 rest advanced research topics and practical applications springer isbn 9781461492986 pautasso cesare zimmermann olaf leymann frank april 2008 restful web services vs big web services proceedings of the 17th international conference on world wide web pp 805 814 doi 10 1145 1367497 1367606 isbn 9781605580852 s2cid 207167438 ferreira otavio nov 2009 semantic web services a restful approach iadis isbn 978 972 8924 93 5 fowler martin 2010 03 18 richardson maturity model steps towards the glory of rest martinfowler com retrieved 2017 06 26 v t e web interfaces server side protocols http v2 v3 encryption webdav cgi scgi fcgi ajp wsrp websocket server apis c nsapi c asapi c isapi com asp jakarta servlet container cli owin asp net handler python wsgi python asgi ruby rack javascript jsgi perl psgi portlet container apache modules mod_include mod_jk mod_lisp mod_mono mod_parrot mod_perl mod_php mod_proxy mod_python mod_wsgi mod_ruby phusion passenger topics web service vs web resource woa vs roa open api webhook application server comparison scripting client side browser apis c npapi liveconnect xpconnect c npruntime c ppapi nacl activex bho xbap web apis whatwg audio canvas dom sse video websockets web messaging web storage web worker xmlhttprequest w3c dom events eme file geolocation indexeddb mse svg webassembly webauthn webgpu webrtc webxr khronos webcl webgl others gears discontinued web sql database discontinued webusb topics ajax and remote scripting vs dhtml browser extension cross site scripting and cors hydration mashup persistent data web idl scripting related topics frontend and backend microservices rest graphql push technology solution stack web page static dynamic web standards web api security web application rich single page progressive web framework v t e internet search types web search engine list metasearch engine multimedia search collaborative search engine cross language search local search vertical search social search image search audio search video search engine enterprise search semantic algorithm semantic search natural language search engine voice search human flesh search engine tools contextual searching cross language information retrieval search by sound search engine marketing search engine optimization evaluation measures search oriented architecture selection based search document retrieval text mining web crawler multisearch federated search search aggregator index web indexing focused crawler...
|
