I am struggling to find any decent links to design patterns, best practice or good, basic architectural principles that should be used in building Actor-based apps. Those few that I know of are:
I\'m trying to learn some Erlang and having trouble figuring out the best approach for a particular problem. Here\'s what I\'m doing:
I have a list of tuples which are http headers.I want to convert the list to a JSON object.I t开发者_运维技巧ry mochijson2 but to no avail.
I\'m working my way through some simple programs for learning Erlang, and whenever I try to use the debugger I get \"Invalid beam file or no abstract code: test_module\" and noth开发者_StackOverflowin
I have a list of JSON objects (received from a nosql db) and want to remove or rename some keys.And then I want to return data as a list of JSON objects once again.
I have the following code loop(Data) -> receive {Key, Value} -> [{Key, Value}|Data]; {Key} -> member(Key, Data);
For my logging I wanted the ability to macro out the statements at compile time, so -define to the rescue!
I tried to do something similar to How to make two different source directories in a Makefile output to one bin directory?, so I have these files (relative to my project root):
By the CAP theorem, it is impossible for a distributed Erlang system to simultaneously provide all three of the following guarantees:
Suppose I have the module test.erl, and inside it is the macro TOTAL: -module(test) -export([...]) -define(TOTAL,(100))
加载中,请稍侯......