background preloader

Representational state transfer

Representational state transfer
Representational State Transfer (REST) is a software architecture style consisting of guidelines and best practices for creating scalable web services.[1][2] REST is a coordinated set of constraints applied to the design of components in a distributed hypermedia system that can lead to a more performant and maintainable architecture.[3] REST has gained widespread acceptance across the Web[citation needed] as a simpler alternative to SOAP and WSDL-based Web services. RESTful systems typically, but not always, communicate over the Hypertext Transfer Protocol with the same HTTP verbs (GET, POST, PUT, DELETE, etc.) used by web browsers to retrieve web pages and send data to remote servers.[3] The REST architectural style was developed by W3C Technical Architecture Group (TAG) in parallel with HTTP 1.1, based on the existing design of HTTP 1.0.[4] The World Wide Web represents the largest implementation of a system conforming to the REST architectural style. Architectural properties[edit]

http://en.wikipedia.org/wiki/Representational_state_transfer

Related:  13/2/7 - 00software generalConceptsLooseLeafSoftware Development

Police in North Carolina Patrol in a Corvette The nonpolice version of the Corvette Z06. Speeders in Wake County, N.C., will have to go pretty fast if they want to outrun the police department’s latest interceptor — a Chevrolet Corvette Z06. The Wake County police recently seized the Corvette from a drug dealer, said David Cooke, the county manager, according to the News & Observer. SOAP Characteristics[edit] SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built. This XML-based protocol consists of three parts: an envelope, which defines what is in the message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing procedure calls and responses.

Scalable Streaming Adaptive Streaming has a good potential to replace widely used progressive download. Adaptive streaming can dynamically adjust the video bit-rate to the varying available bandwidth and prevent prefetching too much future video data when the extra bandwidth is available but the data are eventually left unused. For adaptive streaming, video servers need to maintain multiple copies of the same video with different bit-rates for different clients and clients with different kinds of connectivity, which requires additional server storage and reduces cache hit ratio. Recently, Scalable Video Coding (H.264/SVC) is considered to be able to save server storage and increase hit ratio using the existing web cache infrastructure (click here to see how much storage can be saved). However, a rate adaptation algorithm still needs to be carefully designed for streaming scalable video. In this project, we design and implement a framework for Adaptive Scalable Video (H.264/SVC) Streaming over HTTP.

Micro Service Architecture Conceptually speaking MSA is not particularly difficult to grasp but in practice it does raise many questions. How do these services communicate? What about latency between services? How do you test the services? Stamplay Is IFTTT For Back-End Development If you are a front-end developer, setting up signup forms and integrations with popular APIs can be very painful. Stamplay wants to make back-end development as easy as playing with Lego bricks. The best analogy would be to think of it as an IFTTT for developers.

Egocide and suicide | The Psychology of Me Lately, I’ve been thinking about egocide. (Why does my autocorrect want to change that to “geocode”??) I’m at the end of my rope and climbing back up is not an option. I’ve got to change. Drastically change. RepRap Project RepRap version 1.0 (Darwin) RepRap version 2.0 (Mendel) First part ever made by a Reprap to make a Reprap, fabricated by the Zaphod prototype, by Vik Olliver (2006/09/13) The RepRap project is a British initiative to develop a 3D printer that can print most of its own components.[1] RepRap (short for replicating rapid prototyper) uses an additive manufacturing technique called Fused filament fabrication (FFF) to lay down material in layers; a plastic filament or metal wire is unwound from a coil and supplies material to produce a part. The project calls it Fused Filament Fabrication (FFF) to avoid trademark issues around the "fused deposition modeling" term.

WebDAV Web Distributed Authoring and Versioning (WebDAV) is an extension of the Hypertext Transfer Protocol (HTTP) that allows clients to perform remote Web content authoring operations. A working group of the Internet Engineering Task Force (IETF) defined WebDAV in RFC 4918. The WebDAV working group concluded its work in March 2007, after the Internet Engineering Steering Group (IESG) accepted an incremental update to RFC 2518. Other extensions left unfinished at that time, such as the BIND method, have been finished by their individual authors, independent of the formal working group. Many modern operating systems provide built-in client-side support for WebDAV. History[edit]

Constraints The REST architectural style describes the following six constraints applied to the architecture, while leaving the implementation of the individual components free to design: Client–server Stateless Cacheable Layered system Code on demand (optional) Uniform interface The only optional constraint of REST architecture is code on demand. If a service violates any other constraint, it cannot strictly be referred to as RESTful. Complying with these constraints, and thus conforming to the REST architectural style, will enable any kind of distributed hypermedia system to have desirable emergent properties, such as performance, scalability, simplicity, modifiability, visibility, portability and reliability. by vikasjee Dec 16

The Concept: The client begins sending requests when it is ready to make the transition to a new state. While one or more requests are outstanding, the client is considered to be in transition. The representation of each application state contains links that may be used next time the client chooses to initiate a new state transition. The name "Representational State Transfer" is intended to evoke an image of how a well-designed Web application behaves: a network of web pages (a virtual state-machine), where the user progresses through the application by selecting links (state transitions), resulting in the next page (representing the next state of the application) being transferred to the user and rendered for their use. by vikasjee Dec 16

Related:  IoT Standards and ProtocolsPlay! FrameworkAndroid DevelopmentWeb DevelopmentLINGUAGENS