6 ms·
The project is pre semver 1.0.0, it should not be considering suitable for production. You'll have to be way more specific about what you mean by "handle error
by barracks 15y ago
The project is pre semver 1.0.0, it should not be considering suitable for production.
You'll have to be way more specific about what you mean by "handle errors". Do you mean node to node connection errors? Node to node messaging errors? Errors localized in a custom Hook?
I suggest just reading through the codebase, it's not that big. The entire philosophy is crash only processes which are supervised by Forever. In the current early version of hook.io we usually get let things crash and restart. This isn't idea for guaranteeing delivery of messages, but it's a good start.
- alnayyir 15y ago> The entire philosophy is crash only processes which are supervised by Forever. > we usually get let things crash and restart. >This isn't idea for guaranteeing delivery of messages That is not Erlang.
- changelog 15y agoI think you might be mistaken. From: http://en.wikipedia.org/wiki/Crash-only_software http://en.wikipedia.org/wiki/Crash-only_software Erlang is a computer language originally built by Ericsson for fault-tolerant telephone switches. Programs are structured as modules that can be replaced (hot swapped) without having to restart the entire program. If a module crashes or needs to be updated it can be restarted or replaced without affecting any other part of the program. Within the Open Telecom Platform, which often is used together with Erlang, there exist frameworks to simplify and automate this task.
- alnayyir 15y agoCrash-only is an aspect of Erlang, you've not replaced the entirety of what makes Erlang uniquely useful.
- bradleymeck 15y agoIndeed not, but Erlang is Erlang, Hook.io is Hook.io, and Trolls are Trolls. More perspective on opinions would be helpful to evolving away from problems you see, and/or for the use of understanding your comment.