I am trying to develop an application that can be horizontally scaled. I understand using the socket.io-redis package seems to allow you to emit to a particular socketid from one instance while that connection itself is connected to another machine and the redis connection will take care of the communicating. This in a sense abstracts away the fact that there are multiple servers by just taking care of it transparently.
Are there any provisions within socket.io or another package that allows you to sync normal js objects across servers as well? The alternative as I see it is to use redis pub/sub to keep the state in sync but this feels like it should be a solved problem that one need not reinvent the wheel for.
Could this lead to double spend scenerios? For example, I have 10 LTC on the current system and these guys fork to form a new network. Can I then spend the 10 LTC I have twice, once on their new network and once on the old network?
> We don't need the Litecoin developers.
> We need the majority to support this to make this hardfork work.
This is a pretty interesting comment from the person who is proposing the fork. I wonder how the currency will split if a sizable amount of people switch to this method of mining? Will the devs be forced to accept their fork or will this just split off into a litecoin 2.0 that is ASIC resistant which previously mined coins grandfathered into this new fork
If it is a typo in the ID number, thats understandable. But the social tracking id seems to be wrong too and that also points to the authors id. Can't be wrong twice and have both mistakes point to the same person
> The page for directives is another (in)famous part of the docs that, despite relating to one of the most important aspects of the framework, is often derided as being overly dry
While that used to be true, the directives page recently got updated to provide a much better and simple guide to directives along with plently of code samples -
http://docs.angularjs.org/guide/directive
This idea seems like it would be a much better fit for tablets rather than phones.
You have much more room to play around with on a tablet and perhaps the typical usage patterns of the tablet actually encourages you to swap out your bloks for different purposes.
For example, I could switch to a better but more power consuming Wi-Fi module when I'm at school which usually has crappy coverage but could then swap that out for longer duration battery so that I can watch shows on the train ride back home without compromising on screen brightness or risk the tablet dying before I get home
Haven't seen this mentioned here yet, but Laravel is a great option if you are considering PHP. Laravel 3 is very mature while 4 is just around the corner. It comes with a nice CLI for scaffolding and is very well documented. It also has a nice speed advantage over frameworks like Cake. Laravel + AngularJS makes for really fast development times while creating low maintenance applications.
Words have different meaning to different people. The Feminism label carries a political context that Egalitarianism label does not and not every Egalitarian is automatically a feminist as you claim.