mens

Version:

Isomorphic Mithril Javascript Framework (w/ Websockets)

22 lines • 2.19 kB

JSX

<div class="panel panel-primary"> <div class="panel-heading">Asynchronous Data</div> <div class="panel-body"> The Mens Stack has utilities to render templates with asynchronous data. <ul class="well"> <li>m.fetch(controller, model, callback, skipForRenderFlag); will fetch a model</li> <li>The MENS config key modeler on the server accepts function(data, mensSession, callback) to create a server side data modeler. Once the model lookup is complete, the model should be sent into the callback to reach the client</li> <li>controller should have a session property server side, or the modeler cannot check access permissions. This is done in the route controller with the m.init(this, params) call</li> <li>Multiple m.fetch calls can be made simultaneously, but ideally one model should describe a complete route</li> <li>To render pages without waiting on slow data, send true as the last argument</li> <li>All m.fetch calls must be ran on both the server and the client in order to initialize the route once the page is downloaded. An efficient modeler will cache any lookups.</li> <li>Fetch will automatically set the controllers m.prop properties that are also in the returned model structure</li> <li>m.prop variables declarations and m.fetch calls should take place in the route controller and be passed to children components</li> </ul> Here is some asyncronous data: <ul class="list-group"> <li class="list-group-item">Required Data: {(ctrl.data1() ? ctrl.data1() : 'Pending')}</li> <li class="list-group-item">Defered Data: {(ctrl.data2() ? ctrl.data2() : 'Pending')}</li> </ul> </div> </div>