WebsiteBaker Community Forum
General Community => Off-Topic => Topic started by: erpe0812 on May 05, 2010, 06:00:14 PM
-
Maybe some interisting articles for wb-developers:
http://www.heise.de/newsticker/meldung/Spezifikation-fuer-Content-Management-Interoperabilitaet-fertig-993721.html
or
http://www.oasis-open.org/news/oasis-news-2010-05-04.php
Seems to be interesting for the future.
rgds
erpe
-
It doesn't really make sense for me. It's just a summary of everything that exists already (SOAP / REST / JSON), but WB hasn't used it till yet. So for me it is just an old thing with a new name (like AJAX...).
Yours Michael
-
There is a concept behind this SOAP / REST. OASIS is just something like W3C, it is not the standard itself.
The standard is CMIS.
http://en.wikipedia.org/wiki/Content_Management_Interoperability_Services
CMIS is just a standard that covers the major techniques: SOAP, REST (and probably JSON).
You can find the CMIS standard here:
http://docs.oasis-open.org/cmis/CMIS/v1.0/os/cmis-spec-v1.0.html
What is REST?
Look here:
http://rest.elkstein.org/2008/02/what-is-rest.html
and here
http://en.wikipedia.org/wiki/Representational_State_Transfer
REST stands for Representational State Transfer. [...]
It relies on a stateless, client-server, cacheable communications protocol -- and in virtually all cases, the HTTP protocol is used.
REST is an architecture style for designing networked applications. The idea is that, rather than using complex mechanisms such as CORBA, RPC or SOAP to connect between machines, simple HTTP is used to make calls between machines.
In many ways, the World Wide Web itself, based on HTTP, can be viewed as a REST-based architecture.
RESTful applications use HTTP requests to post data (create and/or update), read data (e.g., make queries), and delete data. Thus, REST uses HTTP for all four CRUD (Create/Read/Update/Delete) operations.
Why should WebsiteBaker use that?
Everybody can answer himself. Nobody needs it.
The major advantage is perhaps:
You don't need a GUI like the WB backend to change anything.
You can change with a good REST-API (yes, you need an API in WB for using REST / SOAP / JSON) anything you like with anything you like. You can use the WebsiteBaker backend - or use the frontend - but you actually don't need it, just the URL.
To give an example:
You perhaps know twitter. And you know perhaps, you can post something with your mobile phone without visiting the twitter website but with an SMS.
So (of course I don't know if twitter uses REST, but it's the idea...) you can update a website with a SMS, without seeing the website.
Yours Michael