
	Where results make sense

Topic: Representational State Transfer

Related Topics

Rest

Web service

List of Web service specifications

Remote procedure call

HTTP cookie

Open standard

Java remote method invocation

Distributed component object model

CORBA

	Fielding Dissertation: CHAPTER 5: Representational State Transfer (REST)
		REST components communicate by transferring a representation of a resource in a format matching one of an evolving set of standard data types, selected dynamically based on the capabilities or desires of the recipient and the nature of the resource.
		Depending on the message control data, a given representation may indicate the current state of the requested resource, the desired state for the requested resource, or the value of some other resource, such as a representation of the input data within a client's query form, or a representation of some error condition for a response.
		An application's state is therefore defined by its pending requests, the topology of connected components (some of which may be filtering buffered data), the active requests on those connectors, the data flow of representations in response to those requests, and the processing of those representations as they are received by the user agent.
	www.ics.uci.edu /~fielding/pubs/dissertation/rest_arch_style.htm (6453 words)

	Representational State Transfer - Wikipedia, the free encyclopedia
		Representational State Transfer (REST) is a software architectural style for distributed hypermedia systems like the world wide web.
		The term originated in a 2000 doctoral dissertation about the web written by Roy Fielding, one of the principal authors of the HTTP protocol specification, and has quickly passed into widespread use in the networking community.
		The application does, however, need to understand the format of the information (representation) returned, which is typically an HTML or XML document of some kind, although it may be an image or any other content.
	en.wikipedia.org /wiki/REST (1176 words)

	RestWiki: How To Parse Rest
		One interpretation of 'state transfer' is that client state 'transfers' as the result of exchanging resource representations with a web service.
		Another interpretation of 'state transfer' is again a 'transition', but this time it's the transition of resource state, not client state.
		In this interpretation, a resource changes state as the result of having state information (and just what constitutes state information can be a deep topic of discussion, in particular whether it implies that end state is explicit or not) transferred from one place in a network to another.
	rest.blueoxen.net /cgi-bin/wiki.pl?HowToParseRest (513 words)

	Tiago Silveira and the world : Weblog
		A state transfer always occurs between a source and a destination, a sender and a receiver.
		But since I'm asking for a representation of an object instead of the object itself, the sender might request that information from another source (potentially in a different representation) and translate from one representation to the other so that the final receiver can use it.
		So we can create chains of state transfers that keep processing different representations of an object until the state is transferred properly from the place where it is to the place where it needs to be.
	jroller.com /page/dukejeffrie?entry=organic_rest (1541 words)

	Web Services: A Realization of SOA > REST (Site not responding. Last check: 2007-10-15)
		Representational State Transfer (REST) is a specific architectural style introduced in [F00].
		This makes up the representation of the resource "current weather in New York City." The processing directives might indicate that the data should not be cached because it changes frequently.
		Services in REST do not maintain the state of an interaction with a requester; that is, if an interaction requires a state, all states must be part of the messages exchanged.
	www.phptr.com /articles/article.asp?p=378135&seqNum=10 (1135 words)

	Web Services: A Realization of SOA > REST (Site not responding. Last check: 2007-10-15)
		Representational State Transfer (REST) is a specific architectural style introduced in [F00].
		This makes up the representation of the resource "current weather in New York City." The processing directives might indicate that the data should not be cached because it changes frequently.
		Services in REST do not maintain the state of an interaction with a requester; that is, if an interaction requires a state, all states must be part of the messages exchanged.
	www.informit.com /articles/article.asp?p=378135&seqNum=10 (1125 words)

	A Matter of Style: Web Services Architectural Patterns
		A representation is the state of a resource captured at a particular instant in time.
		Given that a REST interaction involves only a simple transfer of representations, one can see how a consistent interface can be achieved - there are just not that many possible operations that are needed to perform a simple transfer.
		First, resource representations will be in XML format to derive the benefits of XML as described in Section 3.
	idealliance.org /papers/xml02/dx_xml02/papers/03-02-03/03-02-03.html (5562 words)

	[No title]
		These patterns may seem to have a `REST (REpresentational State Transfer)`_ cast, and that is intentional.
		The variable ``self.state`` is used to keep track of state and to transfer from one state to another.
		And, finally, when the results have been returned, the formatting class is used to produce a representation of the results.
	www.rexx.com /~dkuhlman/twisted_patterns.txt (3427 words)

	A Web-Centric Approach to State Transition
		The transition between states is communicated by a variety of syntactic devices.
		Business rules can be expressed in terms of the state of the transaction at a particular moment rather than in terms of the current state of the transaction.
		REST stands for REpresentational State Transfer - the constant transfer of state (or references to state) back and forth as representations are key to its design.
	www.prescod.net /rest/state_transition.html (2131 words)

	Representational State Transfer
		Representational State Transfer (REST) is a software architectural style for distributed hypermedia systems like the world wide web.
		The term originated in a 2000 doctoral dissertation about the web written by Roy Fielding, one of the principal authors of the HTTP protocol specification, and has quickly passed into widespread use in the networking community.
		The application does, however, need to understand the format of the information (representation) returned, which is typically an HTML or XML document of some kind, although it may be an image or any other content.
	articles.gourt.com /en/REST (1182 words)

	(Site not responding. Last check: 2007-10-15)
		The State Id approach models state implicitly, by application-specific operations on remote state identified by a state identifier that may have meaning only to the Web service to which the operations are directed.
		In contrast, proponents of the State Id approach argue that the design of any particular interface (e.g., one for job management) will typically (a) be relatively simple, (b) involve issues that are not captured by these conventional patterns, and (c) not require all of the features included in the specifications that encode that pattern.
		Multi-job operations exploit the additional registry state maintained by the factory, which as noted in the preceding paragraph, may or may not be the same service.
	www-unix.gridforum.org /mail_archive/dais-wg/2005/05/doc00000.doc (3211 words)

	A Matter of Style: Web Services Architectural Patterns
		A representation is the state of a resource captured at a particular instant in time.
		Given that a REST interaction involves only a simple transfer of representations, one can see how a consistent interface can be achieved - there are just not that many possible operations that are needed to perform a simple transfer.
		First, resource representations will be in XML format to derive the benefits of XML as described in Section 3.
	www.idealliance.org /papers/xml02/dx_xml02/papers/03-02-03/03-02-03.html (5562 words)

	Skyway Software: Terminology
		HyperText Transfer Protocol is the Web's communication standard that defines the universal mechanism for exchanging application-level messages between Web devices.
		In the context of SOA, release management defines the model to ensure the "deploy once run from everywhere" promise can be realized in the SOA environment that becomes exponentially more complicated as services are added.
		Representational State Transfer is a model for web services based solely on HTTP.
	www.skywaysoftware.com /resources/terminology (1063 words)

	Web Services: Lecture 15
		Representational State Transfer (commonly REST) is a style of software architecture for hypermedia systems of global scale, [such as] the World Wide Web
		In the dissertation, Fielding coined the term “Representational State Transfer”, chose the abbreviation “REST”, and defined REST with a set of architectural constraints.
		Stefan goes on to state “I’ve not seen any real-world deployment of any of the more advanced WS-* standards yet, and I have serious doubts that transactions or reliable messaging will be widely deployed soon”.
	www.cs.colorado.edu /~kena/classes/7818/f06/lectures/17/index.html (1491 words)

	Don't throw out the SOAP with the bathwater \| InfoWorld \| Column \| 2005-03-11 \| By Jon Udell (Site not responding. Last check: 2007-10-15)
		Representational State Transfer is fine for Yahoo's services, but it's no cure-all
		Three years ago, mine was one of the voices urging the Web services movement not to lose touch with the Web’s essential nature, as embodied in the architectural style known as REST (Representational State Transfer).
		Its developer FAQ states, “We may provide SOAP interfaces in the future, if there is significant demand.
	weblog.infoworld.com /article/05/03/11/11OPstrategic_1.html?RAPID+... (1340 words)

	REST - ThreatMind
		Fielding Dissertation: Chapter 5 - This chapter introduces and elaborates the Representational State Transfer (REST) architectural style for distributed hypermedia systems, describing the software engineering principles guiding REST and the interaction constraints chosen to retain those principles, while contrasting them to the constraints of other architectural styles.
		In the web services world, REpresentational State Transfer (REST) is a key design idiom that embraces a stateless client-server architecture in which the web services are viewed as resources and can be identified by their URLs.
		Web service clients that want to use these resources access a particular representation by transferring application content using a small globally defined set of remote methods that describe the action to be performed on the resource.
	www.scadasec.net /secwiki/REST (612 words)

	Synthetic Biology: Semantic web ontology/REST
		REST stands for Representation State Transfer, and suggests that what the Web got right is having a small, global set of verbs (GET, POST, PUT, HEAD, etc) applied to a potentially infinite set of nouns (URIs).
		There is a profile of SOAP that supports transferring the state of a resource using only the limited actions of HTTP or some other protocols -- that profile is RESTful.
		That is, each request contains all of the information necessary for a connector to understand the request, independent of any requests that may have preceded it.
	syntheticbiology.org /Semantic_web_ontology/REST.html (350 words)

	Travis Hubbard - REST Web Services Research (Site not responding. Last check: 2007-10-15)
		A representation of the resource is returned (e.g., 1009-xyz.html).
		The representation places the client application in a state.
		Thus, the client application changes (transfers) state with each resource representation.
	www.travishubbard.net /index.php?option=com_content&task=view&id=2&Itemid=9 (162 words)

	Web Dictionary - REST-Words/REST-PukiWiki (Site not responding. Last check: 2007-10-15)
		The Representational State Transfer (REST) style is an abstraction of the...
		Representational State Transfer (REST) is a software architectural style for distributed...
		Representational State Transfer (REST) is a software architectural style for...
	pukiwikimod.com /xbox/modules/pukiwiki/486.html (823 words)

	Ajax and REST, Part 1
		The first is to send a massive amount of state information with each client request, so that each request is context-complete and the server can remain stateless.
		Because the application logic and state reside and execute on the browser, the application's interaction with the server becomes very different from that of a traditional Web application.
		In an Ajax application with a stateful client and stateless services, a server crash/restart can be completely transparent to the user because the server crash can't affect session state, which lives in the user's browser; a stateless service's behavior is idempotent and determined solely by the content of user requests.
	www-128.ibm.com /developerworks/webservices/library/wa-ajaxarch/index.html (3473 words)

	XML.com: Implementing REST Web Services: Best Practices and Guidelines
		Despite the lack of vendor support, Representational State Transfer (REST) web services have won the hearts of many working developers.
		The proxy selects one representation according to preferences set by the client and returns the representation back to the client.
		It should be specific about the type of representation it wants and avoid "/", unless the intention is to retrieve a list of all possible representations.
	www.xml.com /pub/a/2004/08/11/rest.html (952 words)

	Interactions with WebSphere Process Server and WebSphere ESB using Representational State Transfer
		Representational State Transfer (REST) is broad term that definines an architectural style for interaction between systems.
		RESTful interactions are based on HTTP as the communication transport, with URLs and XML documents as the syntax for interactions.
		The article referenced above indicates that the HTTP request uses the "logical" URL, the document sent for information transfer from the requester to the provider, and the document received for information transfer from the provider to the requester.
	www.ibm.com /developerworks/websphere/library/techarticles/0611_flurry/0611_flurry.html?ca=drs- (3869 words)

	REpresentational State Transfer, REST
		The World Wide Web architecture has evolved into a novel architectural style that I call "representational state transfer." Using elements of the client/server, pipe-and-filter, and distributed objects paradigms, this style optimizes the network transfer of representations of a resource.
		A Web-based application can be viewed as a dynamic graph of state representations (pages) and the potential transitions (links) between states.
		The result is an architecture that separates server implementation from the client's perception of resources, scales well with large numbers of clients, enables transfer of data in streams of unlimited size and type, supports intermediaries (proxies and gateways) as data transformation and caching components, and concentrates the application state within the user agent components.
	wiki.tcl.tk /3513 (1085 words)

	Where's the simplicity in Web services?: Builder AU: Manage
		The rallying cry for people who favour simplicity is a technology approach called REST, or Representational State Transfer, a method of building applications by sending XML documents over existing Internet protocols.
		Advocates of Representational State Transfer argue that REST allows the same application-to-application communication that Web services promises.
		Microsoft earlier this month published a white paper stating that Web service protocols are designed to be "autonomous," which allows developers to pick the level of sophistication they need.
	www.builderau.com.au /manage/0,39024662,39131303,00.htm (1350 words)

Try your search on: Qwika (all wikis)