Fact-checked by Grok 2 weeks ago

Roy Fielding

Roy Thomas Fielding is an American computer scientist best known for his pioneering work on the foundational technologies of the , including co-authoring the HTTP/1.1 specification versions (RFC 2068 and RFC 2616) and defining the Representational State Transfer (REST) architectural style in his 2000 doctoral dissertation. As a co-founder of the Project and the (ASF), he played a key role in developing one of the most widely used open-source software, which earned the ACM Software System Award in 1999. Fielding earned his B.S. (1988), M.S. (1993), and Ph.D. (2000) in from the , where his dissertation, titled Architectural Styles and the Design of Network-based Software Architectures, introduced as a scalable framework for distributed hypermedia systems. He also contributed to the standardization of Uniform Resource Identifiers (URIs) as co-author of 3986 in , influencing how resources are identified and accessed on the . Early in his career, Fielding was a founding member of the Apache Group in 1995, serving as ASF Director (1999–2003) and Chairman (1999–2002), and later as Vice President of the Apache HTTP Server Project. Professionally, Fielding has held positions as Chief Scientist at eBuilt (1999–2002) and Day Software (2002–2010, later acquired by Adobe), before joining Adobe as Senior Principal Scientist in 2010, where he continues to focus on web technologies and digital media tools. His innovations have been recognized with awards including the 2000 Appaloosa Award for Vision from O'Reilly Open Source Convention and the 2010 ACM/IEEE International Conference on Software Engineering Most Influential Paper Award for his work on software architectures. Fielding was also the first elected member of the World Wide Web Consortium (W3C) Technical Architecture Group and an inaugural member of MIT Technology Review's TR100 in 1999.

Early Life and Education

Family Background and Early Years

Roy Fielding was born in September 1965 in . He was conceived in , reflecting his family's international ties, and spent part of his there, including a school term in where he learned to read. Fielding's heritage is diverse, encompassing Maori and Kiwi roots from , along with Irish, Scottish, British, and American influences, shaped by his upbringing as a "." His father, an in social sciences at the , played a key role in the family's life in , fostering an environment rich in cultural and academic exposure amid the region's coastal communities. During his high school years in this setting, Fielding developed an early interest in computing and technology, particularly programming, which he pursued as a teenager to secure job opportunities. Upon graduating high school, he immediately began working as a junior programmer, self-teaching languages like BASIC and FORTRAN through summer courses and community college classes. This formative period in Southern California's diverse cultural landscape laid the groundwork for his later transition to formal higher education.

Academic Pursuits

Prior to his undergraduate studies at UC Irvine, Fielding attended in , from 1983 to 1986, focusing on international politics, physics, and humanities. Roy Fielding earned his degree in from the (UC Irvine) in 1988. He continued his studies at the same institution, obtaining a degree in in 1993, with a major emphasis in software. Fielding's doctoral work at UC Irvine focused on for distributed systems, culminating in a in awarded in 2000. His dissertation, titled Architectural Styles and the Design of Network-based Software Architectures, explored principles for designing scalable network protocols and applications. The work was supervised by a committee chaired by Professor Richard N. Taylor, with additional members Professor Mark S. Ackerman and Professor David S. Rosenblum. During his graduate studies, Fielding was actively involved in early web research at UC Irvine's Institute for Software Research (ISR), where he contributed to projects examining software engineering for network-based systems. This academic environment provided the foundation for his later contributions to web standards, bridging theoretical architectural styles with practical implementations in emerging internet technologies.

Professional Career

Early Roles and Apache Involvement

In the mid-1990s, Roy Fielding engaged in several key initiatives focused on web technologies, laying the groundwork for his contributions to open-source projects. He founded, architected, and served as the primary developer of libwww-perl, a Perl4 library for programming, between 1994 and 1995. Additionally, from 1993 to 1997, he acted as the architect and sole developer of MOMspider, a web robot designed for distributed hypertext maintenance. These efforts, conducted during his graduate studies, highlighted his early expertise in technologies and collaborative . In 1995, he also served as a at the Laboratory for within the (W3C). Fielding's involvement deepened with the co-founding of the project in 1995, where he was one of the original group of eight core developers known as the Apache Group. This initiative began as an effort to patch and enhance the public-domain HTTP server NCSA httpd, quickly evolving into a collaborative open-source project that became the foundation for widespread adoption. As a core developer and project chair, Fielding contributed significantly to its architecture and growth, helping establish it as a pivotal tool in early web infrastructure. The Apache Group's success led to the formal incorporation of the Apache Software Foundation (ASF) in 1999, with Fielding serving as its first Chairman from March 1999 to August 2002. In this leadership role, he oversaw the transition to a nonprofit structure, fostering governance policies that supported multiple open-source projects under the ASF umbrella. His tenure emphasized community-driven development and sustainability, principles that influenced the organization's expansion. Later in his career, Fielding's commitment to faced challenges, culminating in his from the OpenSolaris community in February 2008 due to concerns over centralized control and insufficient community autonomy. This decision underscored his advocacy for transparent, decentralized decision-making in collaborative projects, a value rooted in his experiences.

Research and Standards Work

Roy Fielding has been actively participating in the (IETF) since the mid-1990s, authoring or co-authoring over a dozen (RFCs) that form foundational Internet standards. His early contributions include RFC 1808 on relative Uniform Resource Locators in 1995 and RFC 1945 defining HTTP/1.0 in 1996, which established core protocols for communication. These efforts built on the Wide Web's growth since 1990, emphasizing scalable, distributed hypermedia systems. Fielding chaired the IETF HTTP Working Group, overseeing the evolution of HTTP specifications to enhance reliability and performance in network applications. He also contributed significantly to standards, co-authoring 2396 in 1998 for URI generic syntax and its update in 3986 in 2005, which clarified identification and addressing mechanisms essential to architecture. Additional work includes 6570 on URI Templates in 2012, enabling parameterized resource identification. He later co-authored the HTTP/1.1 specification updates in 7230–7235 (2014) and the consolidated HTTP semantics in 9110–9112 (2022), refining core protocols for modern applications. During his doctoral studies, Fielding held a research position as Graduate Student Researcher at the , Irvine's Institute for Software Research from April 1992 to December 1999, where he conducted work on for network-based systems. Following his in 2000, he maintained an affiliation as an external advisor to the Institute, supporting ongoing research in and distributed systems. From 2001 to 2006, Fielding developed the , a , token-based application intended as an efficient alternative to HTTP for applications, supporting interleaved data streams and suitable for both local and long-distance network communications.

Current Position at

Roy Fielding joined in October 2010 following the company's acquisition of Day Software, where he had served as Chief Scientist since February 2002, focusing on advancing architectures. Since October 2010, he has served as Senior Principal Scientist at in . In this capacity, Fielding guides research efforts on technologies, including enhancements to systems derived from Day's legacy products like Experience Manager, and -related implementations critical to Adobe's and tools. His work emphasizes integrating scalable standards into solutions to improve performance and interoperability. Fielding continues to contribute to the evolution of HTTP standards, particularly and related protocols, ensuring their practical application within Adobe's product ecosystem, such as optimizing delivery in the Experience Cloud platform. This integration supports broader industry tools by embedding efficient, standards-compliant networking in content delivery and developer workflows.

Key Contributions

HTTP Protocol Specifications

Roy Fielding co-authored the initial formal specification for HTTP/1.0 in RFC 1945, published in May 1996 by the (IETF) as an informational document. Alongside and Henrik Frystyk Nielsen, Fielding defined the protocol's core request-response architecture, message formats, and essential methods such as GET, HEAD, and , while addressing basic header fields for content types, dates, and authentication. This work codified practices in use since 1990, establishing HTTP as an application-level protocol for distributed hypermedia systems. As the lead author, Fielding advanced the protocol significantly in HTTP/1.1 through RFC 2068, published in January 1997 and co-authored with Jim Gettys, Jeffrey Mogul, Henrik Frystyk Nielsen, and . Key innovations included persistent connections, which enabled multiple requests over a single connection to reduce overhead and latency; caching directives like the introduction of validators (e.g., and Last-Modified) and heuristics for freshness; and , allowing clients and servers to select optimal representations via headers such as Accept and Vary. These enhancements improved efficiency, , and for web applications, with persistent connections alone boosting by minimizing connection setup costs. Fielding continued his influence as editor and co-author of the comprehensive HTTP/1.1 update in RFCs 7230–7235, published in June 2014 alongside Reschke. This standards-track revision obsoleted earlier specifications ( 2068 and 2616), clarifying message syntax and routing ( 7230), semantics and content ( 7231), conditional requests ( 7232), range requests ( 7233), caching ( 7234), and ( 7235). The updates addressed accumulated implementation issues, enhanced security against attacks like cache poisoning, and optimized performance for high-volume traffic, ensuring HTTP's robustness in modern environments. Through his leadership in the IETF HTTP Working Group, particularly the HTTP-bis effort, Fielding guided these revisions to resolve ambiguities and incorporate lessons from widespread deployment. Beyond core HTTP mechanics, Fielding contributed to foundational web addressing standards. He co-authored RFC 3986 in 2005 with and Larry Masinter, defining the generic syntax for Uniform Resource Identifiers (s), including components like scheme, authority, path, query, and fragment, along with processes for resolving relative references and normalization guidelines. This specification standardized URI handling, superseding RFC 2396 and enabling consistent resource identification across protocols. Later, in RFC 6570 published in March 2012, Fielding collaborated with Joe Gregorio, Marc Hadley, Mark Nottingham, and David to introduce URI Templates, a compact syntax for generating URI families through variable expansion, supporting levels of complexity from simple substitution to query parameter encoding. These advancements facilitated dynamic web APIs and uniform resource referencing, underpinning HTTP's extensibility.

REST Architectural Style

Roy Fielding introduced the Representational State Transfer () architectural style in his 2000 PhD dissertation, Architectural Styles and the Design of Network-based Software Architectures, as a novel framework for designing scalable, distributed hypermedia systems. The dissertation evaluated various network-based architectures, deriving incrementally from a null style by applying constraints that capture the essential properties of the modern , such as those observed in the evolution of HTTP/1.1 and standards. Fielding positioned as a hybrid style that combines elements from other architectural approaches, emphasizing roles, constraints, connectors, and data elements to guide the design and evolution of large-scale software architectures. REST is defined as an architectural style for distributed hypermedia systems, where components communicate through standardized interfaces while remaining independent of specific implementation details. It consists of six guiding constraints, which, when applied together, enable properties like , , and evolvability. The first constraint is client-server separation, which divides responsibilities between clients handling user interfaces and servers managing data storage, promoting portability and independent evolution of each. The second, statelessness, requires that each request from a client contain all necessary information for the server to process it, without relying on stored session state, thereby enhancing , reliability, and . Third, cacheability allows responses to be labeled as cacheable or not, enabling intermediaries to reuse data and reduce latency and network load. The fourth constraint, uniform interface, simplifies the architecture by standardizing interactions and decoupling components; it comprises four sub-constraints: identification of resources, manipulation of resources through representations, self-descriptive messages, and hypermedia as the engine of application state (). The fifth, layered system, ensures that components interact only with their adjacent layers, constraining complexity and allowing intermediaries like proxies without affecting the overall system. Finally, is an optional constraint permitting servers to transmit executable code to clients for extending functionality, such as applets or scripts, though it is rarely used in practice. HATEOAS, a cornerstone of the uniform interface, mandates that a client's application state transitions be driven entirely by hypermedia links embedded in server responses, allowing the server to guide interactions without out-of-band knowledge. This principle ensures , as clients discover available actions dynamically from the representations provided, rather than hardcoding URIs or behaviors. REST has evolved into a foundational style for modern web APIs, where it is commonly implemented over HTTP to enable stateless, resource-oriented interactions that support in distributed systems. Fielding has continued to clarify its principles through posts and talks, emphasizing that true REST adherence requires hypermedia-driven state transitions and warning against misapplications that treat REST as mere RPC over HTTP. For instance, in a 2008 post, he stated: "if the engine of application state... is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period," highlighting the frequent omission of in purported REST implementations. These clarifications have reinforced REST's role in guiding the design of evolvable , influencing standards and practices in .

Other Projects and Innovations

In addition to his foundational work on HTTP and REST, Roy Fielding co-founded in 1995 and served as a core developer and project chair for the , contributing to its modular architecture that enabled extensible modules for handling diverse server functionalities. This design allowed the server to become one of the most widely used software globally, powering a significant portion of the internet's infrastructure. His leadership in the project earned the the 1999 ACM Software System Award for its impact on open-source web technologies. Fielding developed the Waka protocol between 2001 and 2006 as a binary, token-based alternative to HTTP, specifically designed to enhance efficiency in low-bandwidth environments such as and wireless networks by aligning with principles for reduced overhead in data transfer. Intended as a lightweight replacement for HTTP/1.1, Waka supported interleaved data and streams to optimize performance in resource-constrained settings, though it did not advance to widespread standardization. Fielding also advanced web caching and proxy standards through early proposals, including the introduction of HTTP Conditional GET in 1994, which enabled efficient validation and reduced unnecessary data transfers in environments. This mechanism, integrated into HTTP specifications, improved for distributed systems by allowing clients to check for updates without full downloads. Through his blog at roy.gbiv.com, launched in the mid-2000s, Fielding has shared extensive writings on design and architecture, clarifying concepts like hypermedia-driven and the semantics of identifiers to guide developers in building scalable network applications. Posts such as "REST must be hypertext-driven" emphasize the importance of URI opacity and standardized media types for maintaining .

Recognition and Impact

Awards and Honors

In 1999, Roy Fielding was selected as one of Technology Review's TR100, recognizing the top 100 innovators under 35 for his foundational contributions to the HTTP protocol and the project. This honor highlighted his early impact on web infrastructure and . That same year, Fielding received the ACM Software System Award as a co-founder of the Apache Group, acknowledging the 's enduring influence on through its role in establishing robust standards. The award, presented by the Association for Machinery, celebrated the project's widespread adoption and contributions to practices. In 2000, Fielding was awarded the Appaloosa Vision Award at the Open Source Convention for his forward-thinking work on standards and interoperability within the project, underscoring his leadership in advancing initiatives. Fielding's dissertation on the Representational State Transfer () architectural style earned the 2010 ICSE Most Influential Paper Award for its 2000 publication, "Principled Design of the Modern Web Architecture," recognizing its profound impact on and as evidenced by extensive citations in ACM and IEEE publications. The paper, co-authored and presented at the International Conference on Software Engineering (sponsored by ACM and IEEE), has been cited over 6,000 times, influencing global standards for network-based applications.

Broader Influence on Web Standards

Roy Fielding's work on HTTP/1.1, as co-author of 2616 and its subsequent updates in RFC 7230–7235, laid the foundational protocol for the web's request-response model, which remains integral to modern web services and APIs despite the rise of later versions. As of 2024 data extended into 2025 trends, approximately 21–22% of websites continue to use HTTP/1.1 as the primary protocol, while and together account for approximately 70% of usage, building directly on HTTP/1.1 semantics for enhanced performance in multiplexed connections. This enduring adoption underscores HTTP/1.1's role in enabling scalable, stateless interactions essential for platforms like AWS and Cloud APIs, where RESTful services—derived from Fielding's architectural principles—power the majority of public interfaces for services such as and . The market, heavily reliant on these standards, reached $6.89 billion in 2025, with 82% of organizations adopting API-first strategies predominantly using over HTTP. Fielding's contributions to URI standards, particularly as co-author of RFC 2396 and its revision in RFC 3986, established a uniform syntax for identifying resources on the web, profoundly influencing the and initiatives. provide the stable, dereferenceable identifiers at the core of principles, allowing resources to be linked across distributed systems much like hyperlinks connect documents, as articulated in foundational W3C guidelines. This framework has enabled the 's vision of machine-readable interconnections, with serving as the backbone for RDF triples and queries in knowledge graphs used by projects like DBpedia and . By decoupling resource identification from representation, Fielding's URI specifications facilitated the web's evolution into a global fabric, supporting in domains from to scientific . Beyond core protocols, Fielding participated in IETF discussions shaping (RFC 7540) and , notably proposing the use of header fields for resource to optimize response delivery in multiplexed . This idea influenced the extensible standardized in 9218, which enhances and by allowing clients to signal preferences for response ordering, addressing latency issues in high-throughput environments like mobile networks and CDNs. , built on for UDP-based transport, integrates these semantics to mitigate , with adoption reaching 36.2% of websites as of November 2025, reflecting Fielding's ongoing input into protocols that adapt the to modern needs such as faster initial connections and better resilience over unreliable networks. Fielding's dissertation introducing the REST architectural style has had significant educational impact, serving as a cornerstone reference in curricula worldwide for teaching distributed systems and web architecture. With over 6,000 citations by 2017 and continuing influence, the work is integrated into courses at institutions like , where it is highlighted for defining REST's constraints like and uniform interfaces. His writings and talks, including IEEE Computing Conversations, are routinely used to illustrate scalable network design, fostering generations of developers who apply REST principles in development and cloud-native applications. This pedagogical legacy ensures REST's principles remain a standard topic in programs, emphasizing conceptual over implementation specifics.

References

  1. [1]
    Vita: Roy Thomas Fielding
    Roy T. Fielding is a Senior Principal Scientist at Adobe Systems Incorporated, a leading provider of creative tools for digital media and digital marketing.
  2. [2]
    Roy Fielding - Engineering and ICS at UCI
    Roy T. Fielding, Senior Principal Scientist at Adobe, is known for his pioneering work on the World Wide Web, open source, and software architecture.
  3. [3]
    Roy T. Fielding
    Roy T. Fielding. Senior Principal Scientist, Adobe Co-founder, Apache HTTP Server Project Director, The Apache Software Foundation
  4. [4]
    Roy Fielding: Geek of the Week - Simple Talk - Redgate Software
    Aug 2, 2010 · Roy Fielding is best known for his work in developing and defining the modern World Wide Web infrastructure by authoring the Internet standards for HTTP.
  5. [5]
    ICS Inductees - UC Irvine
    Roy Fielding PhD 2000, MS 1993, BS 1988. Bio. Roy T. Fielding, Senior Principal Scientist at Adobe, is known for his pioneering work on the World Wide Web ...
  6. [6]
    Architectural Styles and the Design of Network-based Software ...
    Roy Thomas Fielding. 2000. Dissertation Committee: Professor Richard N. Taylor, Chair Professor Mark S. Ackerman Professor David S. Rosenblum. PDF Editions. 1 ...
  7. [7]
    Two Distinguished ISR Alumni Inducted into First ICS Hall of Fame
    Roy T. Fielding Dr. Fielding earned his Ph.D. in 2000, M.S. in 1993, and B.S. 1988–all from ICS. Fielding, a Senior Principal Scientist at Adobe, is known ...Missing: UC Irvine PhD
  8. [8]
    About the Apache HTTP Server Project
    By the end of February, eight core contributors formed the foundation of the original Apache Group: Brian Behlendorf; Roy T. Fielding; Rob Hartill; David ...
  9. [9]
    The Apache Group Incorporates as the Apache Software Foundation
    Jun 30, 1999 · "This is an important step forward for the Apache projects," said Roy T. Fielding, ASF Chairman and co-founder of the Apache HTTP Server Project ...Missing: 1999-2002 | Show results with:1999-2002
  10. [10]
    Watching the ripples » Untangled - Roy T. Fielding
    Feb 21, 2008 · Last week, I resigned from membership in OpenSolaris shortly after midnight on February 14th (Valentine's Day). I won't attempt to explain ...
  11. [11]
    Profile for Roy Fielding - IETF Datatracker
    Senior Principal Scientist at Adobe, co-founder of The ASF, author of ... 129 RFCs · RFC 2616, Jun 1999, Hypertext Transfer Protocol -- HTTP/1.1, 292 RFCs.Missing: participation 1990s
  12. [12]
    draft-fielding-httpbis-http-messaging-00 - IETF Datatracker
    This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process. Select version. 00. Authors, Roy T. Fielding , Julian Reschke
  13. [13]
    https://roy.gbiv.com/untangled/about
  14. [14]
    About Untangled - Roy T. Fielding
    Dr. Fielding continues to serve as a member of The Apache Software Foundation and an external adviser for the University of California's Institute for Software ...Missing: positions | Show results with:positions<|separator|>
  15. [15]
    Roy Fielding - Adobe - LinkedIn
    Roy T. Fielding, Senior Principal Scientist at Adobe, is known for his pioneering work on… · Experience: Adobe · Education: UC Irvine · Location: Tustin ...Missing: research Institute Research
  16. [16]
    HTTP? How it started, how it's going | Adobe Experience Cloud
    Jan 28, 2024 · An interview with Roy Fielding, co-author of the HTTP protocol and inventor of REST, on the evolution of HTTP from early days to current work on ...Missing: interests | Show results with:interests
  17. [17]
    Adobe Developers Live | HTTP? How it started, how it's going.
    Feb 17, 2021 · An interview with Roy Fielding, co-author of the HTTP protocol and inventor of REST, on the evolution of HTTP from early days to current ...Missing: Software acquisition
  18. [18]
    RFC 1945 - Hypertext Transfer Protocol -- HTTP/1.0 - IETF Datatracker
    The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia ...Missing: authored | Show results with:authored
  19. [19]
    RFC 2068: Hypertext Transfer Protocol -- HTTP/1.1
    Below is a merged response that consolidates all the information from the provided segments into a single, comprehensive summary. To maximize detail and clarity, I’ve used a table in CSV format for the authors and key details, followed by a detailed narrative summary and a consolidated list of useful URLs. This ensures all information is retained while maintaining readability and density.
  20. [20]
    RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
    Summary of each segment:
  21. [21]
    [PDF] Fielding's dissertation - UC Irvine
    © Roy Thomas Fielding, 2000. All rights reserved. Page 3. ii. The dissertation of Roy Thomas Fielding is approved and is acceptable in quality and form for ...
  22. [22]
    RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax
    This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security ...
  23. [23]
    RFC 6570 - URI Template - IETF Datatracker
    A URI Template is a compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion.
  24. [24]
    CHAPTER 5: Representational State Transfer (REST)
    This chapter introduces and elaborates the Representational State Transfer (REST) architectural style for distributed hypermedia systems.Missing: contributions persistent
  25. [25]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_2
  26. [26]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_3
  27. [27]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_4
  28. [28]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_5
  29. [29]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_6
  30. [30]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_7
  31. [31]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_5_5
  32. [32]
    https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_2
  33. [33]
    https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
  34. [34]
    REST APIs must be hypertext-driven » Untangled - Roy T. Fielding
    Oct 20, 2008 · I am getting frustrated by the number of people calling any HTTP-based interface a REST API. Today's example is the SocialSite REST API.Missing: modern | Show results with:modern
  35. [35]
    Roy T. Fielding Co-Founder - ACM Awards
    Roy T. Fielding Co-Founder, Digital Library, ACM Software System Award, USA - 1999, Apache citation, Brian Behlendorf, Roy T. Fielding, Rob Hartill, David ...Missing: Foundation 1999-2002
  36. [36]
    https://roy.gbiv.com/protocols/waka/200211_fielding_apachecon.ppt
  37. [37]
    [PPT] Designing a new protocol for the Web - Roy T. Fielding
    How should we design a new application protocol? Define the architectural style. Even a generic protocol must choose one model for evaluation of efficiency, or ...Missing: wireless 2001-2006
  38. [38]
    A conversation with Roy Fielding about HTTP, REST, WebDAV, JSR ...
    Aug 25, 2006 · Waka would be a binary token-based protocol that could work for both local and long-distance communication. It would also interleave data ...Missing: wireless 2001-2006
  39. [39]
    http://www.apacheweek.com/features/appies2000
  40. [40]
    Apache Week. Appaloosa Awards 2000
    Mar 10, 2000 · The Vision Award was for the best ideas to move Apache forward and was won by Ryan Bloom for Apache 2.0 and Roy Fielding for standards and ...
  41. [41]
    HTTP | 2024 | The Web Almanac by HTTP Archive
    Dec 10, 2024 · For desktop, 22% of sites uses HTTP/1.1, 71% uses HTTP/2 and 7% uses HTTP/3. For mobile, 21% uses HTTP/1.1, 70% uses HTTP/2 and 9% uses HTTP/3. ...
  42. [42]
    2025 State of the API Report | Postman
    Eighty-two percent of organizations have adopted some level of an API-first approach, with 25% operating as fully API-first organizations, a 12% increase from ...
  43. [43]
    API Market Size, Growth, and Trends in 2025: A Strategic Overview
    Jun 2, 2025 · The API management market hit $6.89 billion in 2025, and analysts expect it to reach $32.77 billion by 2032. That's a 25% compound annual growth rate.Api Management: The $6.89... · Open Apis: The $3.66 Billion... · Apis Became Revenue Streams
  44. [44]
    draft-ietf-httpbis-priority-03
    Jan 11, 2021 · ... HTTP/2 and HTTP/3 frames for reprioritizing the responses. These ... Roy Fielding presented the idea of using a header field for ...
  45. [45]
    HTTP/3 in the Wild: Why It Beats HTTP/2 Where It Matters Most
    Jun 20, 2025 · Real-World Adoption: HTTP/3 Is Accelerating ; 2022, ~63%, ~22% (as QUIC) ; 2023, ~64%, ~28% ; 2024, ~50%, ~34% ; 2025 (est.) ~62.5%, ~41.5%.
  46. [46]
    [PDF] Reflections on the REST Architectural Style and ``Principled Design ...
    Sep 4, 2017 · Fielding's dissertation has been cited over 6,000 times, according to. Google Scholar; the ICSE/TOIT paper, over 2,000 times. Over the past ...
  47. [47]
    Tufts CS 117: Reading assignment — Distribution Models and HTTP
    RFC 2616 - the specification for the HTTP Protocol; Roy Fielding's PhD Thesis, which introduced REST. This assignment is different from most earlier reading ...Missing: contributions | Show results with:contributions<|control11|><|separator|>
  48. [48]
    Roy T. Fielding: Understanding the REST Style
    Jun 12, 2015 · In this episode Roy T. Fielding reminisces about his PhD dissertation, which defined the Representational State Transfer architectural style.