rest - HATEOAS For a Browser-Based Client Consuming a RESTful Web API -


i designing restful api in asp.net, , designing 1 browser-based client consume restful api (also using asp.net). now, both client , api serviced same solution.

a concept having difficulty wrapping head around how can have logical separation between client , api without compromising synchronization of client page mappings data (from api) displayed in pages. fundamental nature of browser-based application, served in restful manner; discovery of additional client pages via single entry-point , hateoas. also, restful api, resources (application data) discovered @ runtime via single entry-point , hateoas.

for me, concept translates follows:

for client:

welcome page (my client entry-point): www.example.com/home

within html of page, have links to:

www.example.com/profilepage www.example.com/contactspage

etc...

for api:

entry point:

www.api.example.com

my json result (or other media type response) contains links following:

www.api.example.com/resourcetobedisplayedonprofilepage www.api.example.com/resourcetobedisplayedoncontactspage

am correct far in understanding? how can have client know how data respective screen when links in each page's html purely pages?

(my motivation separation scalability , performance purposes. nice able cache layout, styling, , scripting client application pages without context on data being displayed pages. expect stagnancy of page layouts far greater data can displayed within pages, therefore allowing me cache pages far greater amount of time.)

also, given explanation of understanding, can see additional aspects of rest may potentially failing consider in design, or downright wrong?

i think need use xhtml media type instead of json , working link.

you can follow link session: hypermedia apis jon moore described use of xhtml media type instead of json.


Comments

Post a Comment

Popular posts from this blog

javascript - Bootstrap Popover: iOS Safari strange behaviour -

i looking through twitter bootstrap documentation, , i'm interested in implementing dismissible popover when button clicked. here example bootstrap's docs: http://getbootstrap.com/javascript/#dismiss-on-next-click when press "dismissible popover" button os x safari browser works fine. when access same link above ios safari, button not work. is, popover not dismissed on click. why button not working ios safari? the example linked using data-trigger="focus" attribute. try changing data-trigger="click" . <a tabindex="0" class="btn btn-lg btn-danger" role="button" data-toggle="popover" data-trigger="click" title="dismissible popover" data-content="and here's amazing content. it's engaging. right?">dismissible popover</a>
Read more

Magento/PHP - Get phones on all members in a customer group -

i working on custom magento extension. working around adminhtml part , i've created custom form there. here form code: <?php class vivasindustries_smsnotification_block_adminhtml_sms_sendmass_edit_form extends mage_adminhtml_block_widget_form { public function _preparelayout() { $extensionpath = mage::getmoduledir('js', 'vivasindustries_smsnotification'); $head = $this->getlayout()->getblock('head'); $head->addjs('jquery.js'); $head->addjs('vivas.js'); return parent::_preparelayout(); } protected function _prepareform() { $form = new varien_data_form(array( 'id' => 'edit_form', 'action' => $this->geturl('*/*/save', array('id' => $this->getrequest()->get...
Read more

session - Logging Out Using PHP -

i have seen other programs regarding can't seem make work. doing wrong? want achieve after user logged out, going previous pages become restricted. i have 3 php files: 1. sample.php - main page username , password filled in 2. successful.php - user's page after logging in 3. logout.php - destorys session hinder user access pages after logging out sample.php </html> <form action="" method="post"> <table> <tr> <td>username:</td> <td>password:</td> </tr> <tr> <td><input type="text" name="username"></td> <td><input type="password" name="password"></td> </tr> <tr> <td><input type="submit" value="submit" name="submit"></td> </tr> </table> </form> </html> <?php $servername = "localhost"; $username = ...
Read more