Feature request

Is your feature request related to a problem? Please describe.

Currently I need a lock variable for distrubuted states (same [here](https://github.com/mobxjs/mobx-st

We should create a PR to https://github.com/ReactiveX/reactivex.github.io in order to document how RxGo fits in the existing ReactiveX ecosystem and to add RxGo documentation to existing operators.

Adding information on how to test Kefir Observables would be a nice addition to the docs. Wondering if we should put all of that into the main docs site, or have a separate site for testing with chai-kefir, or maybe moving all the docs into a kefirjs.github.io repo & website. Thoughts?

Reading the defer+just solution I remembered there is a fromCallable() in Rx, wouldn't solve the problem described in a simpler way?

http://reactivex.io/documentation/operators/start.html

http://artemzin.com/blog/rxjava-defer-execution-of-function-via-fromcallable/

Is there any advantage in using defer+just instead of fromCallable in your example?

Include Dockerfile in root of project

Request Type

Feature Request

Description

As part of the development and release cycle, please include the Dockerfile generated by docker.sbt in the root of the project so that the container can be built directly from the repo itself.

DocumentMessage is one of the Enterprise Integration Patters and should be supported as well as the Event Message, [Command Message](http://www.enterpriseintegrationpatterns.com/p

Looking to validate IOCs prior submitting them to Cortex in an app I'm developing.

This needs to consist of validating them (is 192.168.001.001 an IP? Or can it be converted to be valid), and also normalising them to be consistent (http://www.google.com/home.html?test=hello%2bworld is normalised to
http://www.google.com/home.html?test=hello+world) so future submissions can be joined on the s

Also for iPad.

With regular Proxy objects you can trigger an infinite loop by modifying an object that was just modified within the set handler:

let validator = {
  set: function(obj, prop, value) {
    if (prop === 'age') {
      if (!Number.isInteger(value)) {
        throw new TypeError('The age is not an integer');
      }
      if (value > 200) {
        throw new RangeError('The age seem

The data registry treats URIs as structured identifiers of datasets. This goes against the idea of "URI Opacity". We should look into this more and at least write up our reasoning.