212:
330:
274:
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 existing architecture of the current implementation and identify which aspects should be considered central to the behavioural and performance requirements of the Web.
278:
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.
202:
An important consequence is that the only identifier that needs to be known is the identifier of the first resource requested, and all other identifiers will be discovered. This means that those identifiers can change without the need to inform the client beforehand and that there can be only loose
230:
started to become available. At the time, there was only a fragmented description of the Web's architecture, and there was pressure in the industry to agree on some standard for the Web interface protocols. For instance, several experimental extensions had been added to the communication protocol
277:
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
273:
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,
265:
and using it as a means to define architectural improvements — and to identify architectural mismatches. Fielding defined REST in his 2000 PhD dissertation "Architectural Styles and the Design of
Network-based Software Architectures" at
410:
The uniform interface constraint is fundamental to the design of any RESTful system. It simplifies and decouples the architecture, which enables each part to evolve independently. The four constraints for this uniform interface are:
261:. 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
298:
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
456:
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
401:
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
314:
The strong 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:
282:
also violated REST constraints 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
931:
419:. 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
323:
441:
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
664:
319:
461:
to other resources that are currently available. There is no need for the client to be hard-coded with information regarding the structure of the server.
718:
199:
links that can be followed to make the state of the system change. Any such request will in turn receive the representation of a resource, and so on.
1189:
1179:
600:
626:
235:, 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.
841:
783:
17:
697:
375:
The REST architectural style defines six guiding constraints. When these constraints are applied to the system architecture, it gains desirable
523:
470:
Several models have been developed to help classify REST APIs according to their adherence to various principles of REST design, such as
183:
in his doctoral dissertation. It means that a server will respond with the representation of a resource (today, it will most often be an
398:
Layered system – A client cannot ordinarily tell whether it is connected directly to the end server, or to an intermediary along the way
901:
1171:
1075:
366:
Reliability in the resistance to failure at the system level in the presence of failures within components, connectors, or data.
42:
1226:
1026:
817:
755:
345:
Performance in component interactions, which can be the dominant factor in user-perceived performance and network efficiency;
1817:
227:
160:
219:
998:
970:
658:
167:
responds to while having little to do with REST as originally formulated—and is often even at odds with the concept.
1156:
267:
1700:
1141:
979:
Pautasso, Cesare; Zimmermann, Olaf; Leymann, Frank (April 2008), "Restful web services vs. "big"' web services",
434:
Resource manipulation through representations: When a client holds a representation of a resource, including any
1822:
1355:
532:
1494:
871:
722:
544:
334:
1221:
1068:
85:
1827:
1710:
1375:
1231:
1211:
592:
538:
505:
416:
379:, such as performance, scalability, simplicity, modifiability, visibility, portability, and reliability.
1184:
622:
452:) – Having accessed an initial URI for the REST application—analogous to a human Web user accessing the
1557:
1251:
1246:
376:
960:
833:
775:
246:
1774:
1544:
1457:
1351:
689:
550:
475:
38:
1812:
1136:
499:
1435:
1779:
1577:
1061:
1036:
748:
SOA with REST: Principles, Patterns & Constraints for
Building Enterprise Solutions with REST
1263:
1101:
341:
The constraints of the REST architectural style affect the following architectural properties:
113:
1499:
1452:
1382:
1151:
121:
63:
648:
249:
together started work on creating formal descriptions of the Web's three primary standards:
1572:
1440:
1271:
415:
Resource identification in requests: Individual resources are identified in requests using
357:
Modifiability of components to meet changing needs (even while the application is running);
389:
Stateless – A specific client does not consume server storage when the client is "at rest"
8:
1784:
1567:
1405:
1194:
893:
511:
1241:
100:
system, such as the Web, should behave. The REST architectural style emphasises uniform
1682:
1504:
1370:
1004:
806:
136:
105:
980:
746:
Erl, Thomas; Carlyle, Benjamin; Pautasso, Cesare; Balasubramanian, Raj (2012). "5.1".
351:
allowing the support of large numbers of components and interactions among components;
1695:
1326:
1022:
1008:
994:
966:
923:
813:
751:
654:
287:
262:
125:
1764:
1745:
1686:
1656:
1646:
986:
283:
520: – Collection of loosely coupled services used to build computer applications
1769:
1740:
1199:
1016:
140:
88:
that was created to guide the design and development of the architecture for the
1562:
1534:
1489:
326:, and a low entry-barrier for content readers, content authors and developers.
308:
92:. REST defines a set of constraints for how the architecture of a distributed,
89:
1806:
1791:
1752:
1730:
1617:
1519:
1467:
1204:
517:
438:
attached, it has enough information to modify or delete the resource's state.
386:
Client/Server – Client are separated from servers by a well-defined interface
315:
211:
129:
990:
1690:
1346:
1216:
780:
Architectural Styles and the Design of
Network-based Software Architectures
694:
Architectural Styles and the Design of
Network-based Software Architectures
597:
Architectural Styles and the Design of
Network-based Software Architectures
556:
279:
232:
215:
180:
164:
1587:
1524:
1418:
1396:
1342:
1092:
348:
329:
109:
928:
Conference: Web
Services (ICWS), 2015 IEEE International Conference OnAt
1529:
1509:
1484:
1430:
1423:
1311:
1291:
442:
196:
97:
1552:
1514:
1306:
1161:
493:
458:
453:
159:
and what are widely considered best practices regarding the "verbs" (
151:, although this term is more commonly associated with the design of
1735:
1592:
1360:
1321:
1316:
1296:
1286:
1281:
559: – Service offered between electronic devices via the internet
435:
93:
982:
Proceedings of the 17th international conference on World Wide Web
135:
REST has been employed throughout the software industry to create
1705:
1651:
1447:
1365:
1146:
1084:
1053:
863:
745:
449:
360:
Visibility of communication between components by service agents;
117:
1662:
1602:
1597:
1476:
1276:
1129:
1119:
1114:
650:
Media, Society, World: Social Theory and
Digital Media Practice
363:
Portability of components by moving program code with the data;
921:
502: – Layer in the internet ecosystem addressing bottlenecks
1630:
1625:
1607:
1413:
1124:
1037:"Richardson Maturity Model: steps towards the glory of REST"
1236:
1109:
428:
420:
258:
254:
243:
192:
184:
152:
496: – URL intended to improve the usability of a website
1582:
1301:
978:
962:
REST: Advanced
Research Topics and Practical Applications
424:
337:
of the concepts expressed in the REST architectural style
250:
239:
188:
179:
was introduced and defined in 2000 by computer scientist
156:
101:
431:—none of which are the server's internal representation.
561:
Pages displaying short descriptions of redirect targets
226:
The Web began to enter everyday use in 1993–1994, when
959:
Pautasso, Cesare; Wilde, Erik; Alarcon, Rosa (2014),
719:"Fielding discussing the definition of the REST term"
958:
776:"Chapter 2: Network-based Application Architectures"
528:
Pages displaying wikidata descriptions as a fallback
593:"Chapter 5: Representational State Transfer (REST)"
526: – descriptions of computer network interfaces
805:
59:Architectural style for client-server applications
750:. Upper Saddle River, New Jersey: Prentice Hall.
392:Cache – Responses indicate their own cacheability
1804:
924:"A Maturity Model for Semantic RESTful Web APIs"
553: – Architectural pattern in software design
547: – Architectural pattern in software design
541: – Architectural pattern in software design
535: – Architectural pattern in software design
311:as possible to facilitate large-scale adoption.
741:
739:
448:Hypermedia as the engine of application state (
855:
803:
797:
769:
767:
586:
584:
582:
580:
578:
576:
144:
1069:
524:Overview of RESTful API Description Languages
514: – Namespace identifier assigned by IANA
112:of interactions between them, and creating a
922:Ivan Salvadori, Frank Siqueira (June 2015).
736:
382:The formal REST constraints are as follows:
370:
782:(Ph.D.). University of California, Irvine.
764:
696:(Ph.D.). University of California, Irvine.
690:"Chapter 6: Experience and Evaluation"
599:(Ph.D.). University of California, Irvine.
573:
293:
23:
1076:
1062:
812:. Sebastopol, California: O'Reilly Media.
322:and independent deployment of components,
24:
1018:Semantic Web Services: A RESTful Approach
195:document) and that resource will contain
1014:
773:
687:
620:
590:
465:
328:
210:
32:This is an accepted version of this page
804:Richardson, Leonard; Ruby, Sam (2007).
646:
14:
1805:
1034:
143:. An application that adheres to the
1057:
861:
480:the Classification of HTTP-based APIs
683:
681:
623:"REST APIs must be hypertext driven"
405:
203:coupling between client and server.
653:. London: Polity Press. p. 2.
56:
1083:
952:
721:. groups.yahoo.com. Archived from
354:Simplicity of a uniform interface;
57:
1839:
874:from the original on 7 April 2019
678:
934:from the original on 2024-02-27
915:
904:from the original on 2023-01-29
886:
844:from the original on 2024-02-24
786:from the original on 2014-12-16
700:from the original on 2023-03-26
667:from the original on 2024-02-27
629:from the original on 2010-03-18
621:Fielding, Roy T. (2008-10-20).
603:from the original on 2021-05-13
177:representational state transfer
147:may be informally described as
18:Representational State Transfer
826:
711:
640:
614:
533:Resource-oriented architecture
145:REST architectural constraints
13:
1:
1035:Fowler, Martin (2010-03-18).
1015:Ferreira, Otavio (Nov 2009),
894:"Classification of HTTP APIs"
862:Gupta, Lokesh (2 June 2018).
774:Fielding, Roy Thomas (2000).
688:Fielding, Roy Thomas (2000).
591:Fielding, Roy Thomas (2000).
566:
545:Service-oriented architecture
170:
104:, independent deployment of
86:software architectural style
7:
1818:Hypertext Transfer Protocol
539:Resource-oriented computing
506:Domain application protocol
487:
10:
1844:
206:
61:
1723:
1675:
1639:
1616:
1543:
1475:
1466:
1404:
1395:
1335:
1262:
1170:
1100:
1091:
941:– via Researchgate.
551:Web-oriented architecture
476:Richardson Maturity Model
377:non-functional properties
371:Architectural constraints
335:entity-relationship model
324:large-grain data transfer
120:to reduce user-perceived
500:Content delivery network
294:Architectural properties
228:websites for general use
39:latest accepted revision
991:10.1145/1367497.1367606
838:www.visual-paradigm.com
647:Couldry, Nick (2012).
483:the W S maturity model
338:
223:
141:web-based applications
1823:Software architecture
466:Classification models
332:
214:
64:Rest (disambiguation)
985:, pp. 805–814,
808:RESTful Web Services
320:anarchic scalability
114:layered architecture
62:For other uses, see
834:"What is REST API?"
725:on November 5, 2015
512:List of URI schemes
29:Page version status
1828:Web 2.0 neologisms
1371:Application server
870:. RESTfulAPI.net.
339:
263:protocol standards
231:(HTTP) to support
224:
128:, and encapsulate
35:
1800:
1799:
1719:
1718:
1696:Browser extension
1671:
1670:
1391:
1390:
1327:Phusion Passenger
1028:978-972-8924-93-5
868:REST API Tutorial
819:978-0-596-52926-0
757:978-0-13-701251-0
406:Uniform interface
395:Uniform interface
303:(client) and the
47:18 September 2024
26:
16:(Redirected from
1835:
1765:Web API security
1687:Remote scripting
1657:Web SQL Database
1473:
1472:
1402:
1401:
1098:
1097:
1078:
1071:
1064:
1055:
1054:
1050:
1048:
1047:
1041:martinfowler.com
1031:
1011:
975:
943:
942:
940:
939:
919:
913:
912:
910:
909:
890:
884:
883:
881:
879:
859:
853:
852:
850:
849:
830:
824:
823:
811:
801:
795:
794:
792:
791:
771:
762:
761:
743:
734:
733:
731:
730:
715:
709:
708:
706:
705:
685:
676:
675:
673:
672:
644:
638:
637:
635:
634:
625:. roy.gbiv.com.
618:
612:
611:
609:
608:
588:
562:
529:
21:
1843:
1842:
1838:
1837:
1836:
1834:
1833:
1832:
1813:Cloud standards
1803:
1802:
1801:
1796:
1770:Web application
1715:
1667:
1635:
1612:
1539:
1462:
1387:
1331:
1258:
1237:JavaScript JSGI
1217:ASP.NET Handler
1200:Jakarta Servlet
1166:
1087:
1082:
1045:
1043:
1029:
1001:
973:
955:
953:Further reading
949:
947:
946:
937:
935:
920:
916:
907:
905:
892:
891:
887:
877:
875:
860:
856:
847:
845:
832:
831:
827:
820:
802:
798:
789:
787:
772:
765:
758:
744:
737:
728:
726:
717:
716:
712:
703:
701:
686:
679:
670:
668:
661:
645:
641:
632:
630:
619:
615:
606:
604:
589:
574:
569:
560:
527:
490:
468:
408:
373:
296:
209:
173:
76:presentational
67:
60:
55:
54:
53:
52:
51:
50:
34:
22:
15:
12:
11:
5:
1841:
1831:
1830:
1825:
1820:
1815:
1798:
1797:
1795:
1794:
1789:
1788:
1787:
1782:
1777:
1767:
1762:
1761:
1760:
1750:
1749:
1748:
1743:
1733:
1727:
1725:
1721:
1720:
1717:
1716:
1714:
1713:
1708:
1703:
1698:
1693:
1679:
1677:
1673:
1672:
1669:
1668:
1666:
1665:
1660:
1659:(formerly W3C)
1654:
1649:
1643:
1641:
1637:
1636:
1634:
1633:
1628:
1622:
1620:
1614:
1613:
1611:
1610:
1605:
1600:
1595:
1590:
1585:
1580:
1575:
1570:
1565:
1560:
1555:
1549:
1547:
1541:
1540:
1538:
1537:
1535:XMLHttpRequest
1532:
1527:
1522:
1517:
1512:
1507:
1502:
1497:
1492:
1487:
1481:
1479:
1470:
1464:
1463:
1461:
1460:
1455:
1450:
1445:
1444:
1443:
1433:
1428:
1427:
1426:
1421:
1410:
1408:
1399:
1393:
1392:
1389:
1388:
1386:
1385:
1380:
1379:
1378:
1368:
1363:
1358:
1349:
1339:
1337:
1333:
1332:
1330:
1329:
1324:
1319:
1314:
1309:
1304:
1299:
1294:
1289:
1284:
1279:
1274:
1268:
1266:
1264:Apache modules
1260:
1259:
1257:
1256:
1255:
1254:
1244:
1239:
1234:
1229:
1224:
1219:
1214:
1209:
1208:
1207:
1197:
1192:
1187:
1182:
1176:
1174:
1168:
1167:
1165:
1164:
1159:
1154:
1149:
1144:
1139:
1134:
1133:
1132:
1127:
1122:
1117:
1106:
1104:
1095:
1089:
1088:
1085:Web interfaces
1081:
1080:
1073:
1066:
1058:
1052:
1051:
1032:
1027:
1012:
999:
976:
971:
954:
951:
945:
944:
914:
898:algermissen.io
885:
864:"REST HATEOAS"
854:
825:
818:
796:
763:
756:
735:
710:
677:
659:
639:
613:
571:
570:
568:
565:
564:
563:
554:
548:
542:
536:
530:
521:
515:
509:
503:
497:
489:
486:
485:
484:
481:
478:
467:
464:
463:
462:
446:
439:
432:
407:
404:
403:
402:
399:
396:
393:
390:
387:
372:
369:
368:
367:
364:
361:
358:
355:
352:
346:
295:
292:
247:working groups
208:
205:
172:
169:
130:legacy systems
90:World Wide Web
84:ransfer) is a
58:
36:
30:
27:
25:
9:
6:
4:
3:
2:
1840:
1829:
1826:
1824:
1821:
1819:
1816:
1814:
1811:
1810:
1808:
1793:
1792:Web framework
1790:
1786:
1783:
1781:
1778:
1776:
1773:
1772:
1771:
1768:
1766:
1763:
1759:
1756:
1755:
1754:
1753:Web standards
1751:
1747:
1744:
1742:
1739:
1738:
1737:
1734:
1732:
1731:Microservices
1729:
1728:
1726:
1722:
1712:
1709:
1707:
1704:
1702:
1699:
1697:
1694:
1692:
1688:
1684:
1681:
1680:
1678:
1674:
1664:
1661:
1658:
1655:
1653:
1650:
1648:
1645:
1644:
1642:
1638:
1632:
1629:
1627:
1624:
1623:
1621:
1619:
1615:
1609:
1606:
1604:
1601:
1599:
1596:
1594:
1591:
1589:
1586:
1584:
1581:
1579:
1576:
1574:
1571:
1569:
1566:
1564:
1561:
1559:
1556:
1554:
1551:
1550:
1548:
1546:
1542:
1536:
1533:
1531:
1528:
1526:
1523:
1521:
1520:Web messaging
1518:
1516:
1513:
1511:
1508:
1506:
1503:
1501:
1498:
1496:
1493:
1491:
1488:
1486:
1483:
1482:
1480:
1478:
1474:
1471:
1469:
1465:
1459:
1456:
1454:
1451:
1449:
1446:
1442:
1439:
1438:
1437:
1434:
1432:
1429:
1425:
1422:
1420:
1417:
1416:
1415:
1412:
1411:
1409:
1407:
1403:
1400:
1398:
1394:
1384:
1381:
1377:
1374:
1373:
1372:
1369:
1367:
1364:
1362:
1359:
1357:
1353:
1350:
1348:
1344:
1341:
1340:
1338:
1334:
1328:
1325:
1323:
1320:
1318:
1315:
1313:
1310:
1308:
1305:
1303:
1300:
1298:
1295:
1293:
1290:
1288:
1285:
1283:
1280:
1278:
1275:
1273:
1270:
1269:
1267:
1265:
1261:
1253:
1250:
1249:
1248:
1245:
1243:
1240:
1238:
1235:
1233:
1230:
1228:
1225:
1223:
1220:
1218:
1215:
1213:
1210:
1206:
1203:
1202:
1201:
1198:
1196:
1193:
1191:
1188:
1186:
1183:
1181:
1178:
1177:
1175:
1173:
1169:
1163:
1160:
1158:
1155:
1153:
1150:
1148:
1145:
1143:
1140:
1138:
1135:
1131:
1128:
1126:
1123:
1121:
1118:
1116:
1113:
1112:
1111:
1108:
1107:
1105:
1103:
1099:
1096:
1094:
1090:
1086:
1079:
1074:
1072:
1067:
1065:
1060:
1059:
1056:
1042:
1038:
1033:
1030:
1024:
1020:
1019:
1013:
1010:
1006:
1002:
1000:9781605580852
996:
992:
988:
984:
983:
977:
974:
972:9781461492986
968:
964:
963:
957:
956:
950:
933:
929:
925:
918:
903:
899:
895:
889:
873:
869:
865:
858:
843:
839:
835:
829:
821:
815:
810:
809:
800:
785:
781:
777:
770:
768:
759:
753:
749:
742:
740:
724:
720:
714:
699:
695:
691:
684:
682:
666:
662:
660:9780745639208
656:
652:
651:
643:
628:
624:
617:
602:
598:
594:
587:
585:
583:
581:
579:
577:
572:
558:
555:
552:
549:
546:
543:
540:
537:
534:
531:
525:
522:
519:
518:Microservices
516:
513:
510:
507:
504:
501:
498:
495:
492:
491:
482:
479:
477:
473:
472:
471:
460:
455:
451:
447:
444:
440:
437:
433:
430:
426:
422:
418:
414:
413:
412:
400:
397:
394:
391:
388:
385:
384:
383:
380:
378:
365:
362:
359:
356:
353:
350:
347:
344:
343:
342:
336:
331:
327:
325:
321:
317:
316:extensibility
312:
310:
306:
305:origin server
302:
291:
289:
285:
281:
275:
271:
269:
264:
260:
256:
252:
248:
245:
241:
236:
234:
229:
221:
217:
213:
204:
200:
198:
194:
190:
186:
182:
178:
168:
166:
162:
158:
154:
150:
146:
142:
138:
133:
131:
127:
123:
119:
115:
111:
107:
103:
99:
95:
91:
87:
83:
79:
75:
71:
65:
48:
44:
40:
33:
28:
19:
1757:
1406:Browser APIs
1347:Web resource
1044:. Retrieved
1040:
1017:
981:
965:, Springer,
961:
948:
936:. Retrieved
930:. New York.
927:
917:
906:. Retrieved
897:
888:
876:. Retrieved
867:
857:
846:. Retrieved
837:
828:
807:
799:
788:. Retrieved
779:
747:
727:. Retrieved
723:the original
713:
702:. Retrieved
693:
669:. Retrieved
649:
642:
631:. Retrieved
616:
605:. Retrieved
596:
557:Web services
469:
409:
381:
374:
340:
313:
304:
300:
297:
280:HTTP cookies
276:
272:
237:
225:
218:speaking at
216:Roy Fielding
201:
181:Roy Fielding
176:
174:
161:HTTP methods
148:
134:
81:
77:
73:
69:
68:
46:
37:This is the
31:
1785:Progressive
1780:Single-page
1588:WebAssembly
1568:Geolocation
1525:Web storage
1431:C NPRuntime
1419:LiveConnect
1397:Client-side
1343:Web service
1272:mod_include
1227:Python ASGI
1222:Python WSGI
1172:Server APIs
1093:Server-side
349:Scalability
307:must be as
139:, reliable
116:to promote
110:scalability
1807:Categories
1553:DOM events
1530:Web worker
1515:WebSockets
1376:comparison
1312:mod_python
1292:mod_parrot
1125:Encryption
1046:2017-06-26
938:2020-12-14
908:2023-01-29
848:2024-02-24
790:2014-04-12
729:2017-08-08
704:2023-06-21
671:2021-06-09
633:2016-07-06
607:2004-08-17
567:References
459:hyperlinks
443:media type
301:user agent
197:hypermedia
124:, enforce
106:components
102:interfaces
98:hypermedia
1711:Scripting
1573:IndexedDB
1424:XPConnect
1383:Scripting
1307:mod_proxy
1252:container
1242:Perl PSGI
1232:Ruby Rack
1205:container
1162:WebSocket
1102:Protocols
1021:, IADIS,
1009:207167438
878:March 10,
494:Clean URL
454:home page
268:UC Irvine
175:The term
171:Principle
137:stateless
1736:Web page
1593:WebAuthn
1468:Web APIs
1361:Open API
1322:mod_ruby
1317:mod_wsgi
1297:mod_perl
1287:mod_mono
1282:mod_lisp
1212:CLI OWIN
932:Archived
902:Archived
872:Archived
842:Archived
784:Archived
698:Archived
665:Archived
627:Archived
601:Archived
488:See also
436:metadata
288:security
165:resource
126:security
94:Internet
43:reviewed
1746:Dynamic
1706:Web IDL
1652:GraphQL
1618:Khronos
1448:ActiveX
1436:C PPAPI
1414:C NPAPI
1366:Webhook
1302:mod_php
1247:Portlet
1195:COM ASP
1190:C ISAPI
1185:C ASAPI
1180:C NSAPI
450:HATEOAS
284:privacy
233:proxies
207:History
155:-based
149:RESTful
122:latency
118:caching
96:-scale
1741:Static
1724:Topics
1701:Mashup
1676:Topics
1663:WebUSB
1640:Others
1603:WebRTC
1598:WebGPU
1490:Canvas
1477:WHATWG
1336:Topics
1277:mod_jk
1130:WebDAV
1025:
1007:
997:
969:
816:
754:
657:
427:or as
257:, and
108:, the
1691:DHTML
1647:Gears
1631:WebGL
1626:WebCL
1608:WebXR
1510:Video
1485:Audio
1005:S2CID
508:(DAP)
309:loose
220:OSCON
80:tate
1775:Rich
1758:REST
1689:vs.
1685:and
1683:Ajax
1563:File
1495:CORS
1458:XBAP
1441:NaCl
1354:vs.
1345:vs.
1157:WSRP
1147:FCGI
1142:SCGI
1110:HTTP
1023:ISBN
995:ISBN
967:ISBN
880:2019
814:ISBN
752:ISBN
655:ISBN
474:the
429:JSON
421:HTML
417:URIs
286:and
259:HTML
255:HTTP
244:IETF
242:and
238:The
222:2008
193:JSON
185:HTML
163:) a
157:APIs
153:HTTP
70:REST
1583:SVG
1578:MSE
1558:EME
1545:W3C
1505:SSE
1500:DOM
1453:BHO
1356:ROA
1352:WOA
1152:AJP
1137:CGI
987:doi
425:XML
333:An
251:URI
240:W3C
191:or
189:XML
45:on
1809::
1120:v3
1115:v2
1039:.
1003:,
993:,
926:.
900:.
896:.
866:.
840:.
836:.
778:.
766:^
738:^
692:.
680:^
663:.
595:.
575:^
423:,
318:,
290:.
270:.
253:,
187:,
132:.
74:Re
41:,
1077:e
1070:t
1063:v
1049:.
989::
911:.
882:.
851:.
822:.
793:.
760:.
732:.
707:.
674:.
636:.
610:.
445:.
82:T
78:S
72:(
66:.
49:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
