Erlang OTP I/O - A few questions -
i have read 1 of erlang's biggest adopters telecom industry. i'm assuming use send binary data between nodes , provide easy redundancy, efficiency, , parallelism.
does erlang send binary central node?
is directly responsible parsing binary data actual voice? or fed language/program via ports?
is responsible speed in telephone call, speed in delay between me saying , hearing it.
is possible erlang solely used ease in parallel behavior , c++ or similar processing speed in sequential functions?
i can guess @ how things implemented in actual telecom switches, can recommend approach take:
first, implement in erlang, including of low-level stuff. won't scale since signal processing costly. prototype however, works , can make calls , whatnot.
second, decide on performance bottlenecks. can push them c(++) , factor of 10 or can push them fpga , factor of 100. can cmos work , factor of 1000. price of latter approach steeper, decide need , go buy that.
erlang remains in control of control backplane in sense of happens when push buttons call setup , on. once call has been allocated, hand on channel lower layer. atm switching easier here because once connection set don't need change (atm connection-oriented, ip packet-oriented).
erlangs distribution features there providing redundancy in control backplane. is, synchronize tables of call setups , on between multiple nodes facilitate node takeover in case of hardware failure.
the trick use ports , nifs post prototype speed slower parts of program.
Comments
Post a Comment