diso.core

Created: 2014-05-19 11:25
Updated: 2017-12-27 20:48
License: other

README.md

diso.core

0.0.33

Notes

The top level export includes an object with two properties:

var Core = require('diso.core');
var Client = Core.Client;
var Server = Core.Server;

However, this introduces an issue for clientside bundlers such as Browserify, which would try to include Server code in the client bundle, causing failures from serverside-only libs

For this reason the js builds are exported to the top level of the package so that client and server directories can be required independently as follows

var Client = require('diso.core/Client');
var Server = require('diso.core/Server');

Description

Client/Server/Derp

Research

documentation

frameworks to check out

security

production environments

queues to decouple server and workers / message handlers

derp rest

http://en.wikipedia.org/wiki/Representational_state_transfer http://en.wikipedia.org/wiki/HATEOAS http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm http://en.wikipedia.org/wiki/HTTP https://github.com/prettymuchbryce/node-http-status/blob/master/lib/httpstatus.js http://en.wikipedia.org/wiki/List_of_HTTP_status_codes https://dev.twitter.com/docs/error-codes-responses https://github.com/visionmedia/express/blob/master/examples/route-map/index.js#L47

Todo

  • headers, status from page load -> container
  • styles, scripts
  • metadata updating / between redirects / client page changes
  • PAGE TRANSITIONS
  • PAGE MODALS
  • Introduce queue / messaging intermediary so that socket connections can be scaled across multiple servers. in process, requesthandler / ServerActions need to be replaceable with acceptor pattern that converts http request into "pageRequest" that is pushed onto queue and handled by consumers
Cookies help us deliver our services. By using our services, you agree to our use of cookies Learn more