REST Architecture

Hi Peers,
What is REST architecture? How is it related to Interwoven?

Thanking you in advance.

Find more posts tagged with

Comments

Hi Peers,
What is REST architecture? How is it related to Interwoven?

Thanking you in advance.

Hi,

REST (representational state transfer): is an approach for getting information content from a Web site by reading a designated Web page that contains an XML file that describes and includes the desired content.

Basically you can say REST-style architectures consist of clients and servers. Clients initiate requests to servers and servers process requests and return appropriate responses.
you can get several documents if you google it.

HTH.

robot

Hi,

REST (representational state transfer): is an approach for getting information content from a Web site by reading a designated Web page that contains an XML file that describes and includes the desired content.

Basically you can say REST-style architectures consist of clients and servers. Clients initiate requests to servers and servers process requests and return appropriate responses.
you can get several documents if you google it.

HTH.

Thanks Santosh but I wanted to know more about how it is releated to SOAP and so on.
Peers please find time to give your kind information.

Thanks in advance.

HeMan10

For one it doesn't use SOAP. It uses basic HTTP protocol to serve requests. Usually the requests are basic CRUD operations. And the requests are basic GET urls with a query string for various parameters.

santosh013

REST and SOAP are two different things.
REST is simpler to use than the well-known SOAP (Simple Object Access Protocol) approach,
which requires writing or using a provided server program (to serve data)
and a client program (to request data).
SOAP, however, offers potentially more capability than REST.

Crsb

http://www.google.com/search?q=Rest

robot

http://www.google.com/search?q=Rest

Thanks CRSB but what I wanted to know is that have you implemented it in Interwoven?
If yes then please shed your experience.
Thanks.

Crsb

I haven't implemented it for TeamSite or LiveSite just because it is already implemented OOTB for LSCS query. if you have access to iwov docs, you should be able to find all about how REST API is implemented for LSCS.
the doc name is lscs_(version)_tech_ref.pdf and see Application Programming Interface chapter around page 26.

ccprofessional

robot -

REST based queries are used when you have an application that needs data from the IDOL repository that LSCS relies on. From your brief, rather un educated question, it appears like you are more intrigued by the jargon than actually solving the problem. Yea, call me biased.

What is the real problem you are trying to solve?

robot

robot -

REST based queries are used when you have an application that needs data from the IDOL repository that LSCS relies on. From your brief, rather un educated question, it appears like you are more intrigued by the jargon than actually solving the problem. Yea, call me biased.

What is the real problem you are trying to solve?

No Sir you are not biased, you are only 40 short of platinum mark and reply me and then it will only be 39.

Thanks santosh,heman and crsb for your time.

Thanks.

ISCBorisB

No Sir you are not biased, you are only 40 short of platinum mark and reply me and then it will only be 39.

Thanks santosh,heman and crsb for your time.

Thanks.

REST and SOAP are not "Architectures". You can not compare them directly.
Both are, for the lack of better term "approaches" to WEB-based Client/Server communication.

At it's core SOAP is a protocol for exchanging XML-based messages, nothing more. Together
with the collection of "WS" Tools like WSDL, WS-Security, WS-This and WS-that it provides
scalable Transport framework that *may* support distributed environments, has some
error handling etc. As you can see, you will need some tools to develop, integrate and run it.

REST is not even a protocol. It's a fancy name for a hodge-podge collection of HTTP 1 methods like
get, post, delete and so on. Sure enough, all that is tied to HTTP transport. It is much simpler
than SOAP, does not require that many development and run-time tools etc. The disadvantage
(or perhaps it's biggest advantage) is that it is as good as your code. There is nothing built-in for
scalability, security, error processing, you name it.

robot

REST and SOAP are not "Architectures". You can not compare them directly.
Both are, for the lack of better term "approaches" to WEB-based Client/Server communication.

At it's core SOAP is a protocol for exchanging XML-based messages, nothing more. Together
with the collection of "WS" Tools like WSDL, WS-Security, WS-This and WS-that it provides
scalable Transport framework that *may* support distributed environments, has some
error handling etc. As you can see, you will need some tools to develop, integrate and run it.

REST is not even a protocol. It's a fancy name for a hodge-podge collection of HTTP 1 methods like
get, post, delete and so on. Sure enough, all that is tied to HTTP transport. It is much simpler
than SOAP, does not require that many development and run-time tools etc. The disadvantage of course
is that it is as good as your code. There is nothing built-in for scalability, security, error processing,
you name it.

Thanks Boris, it really helped me in understanding the thing.
Thanks once again for your nice piece of info. as well as time.

Thanks.