Hi Jose :) > I have to say, however, that I agree with Fred on this topic. Especially with > the considerations that a restart_delay as an integer value is not enough. I > would even say jitter is more important than backoff in many cases, and > supporting both exponential backoffs and jitter will require more > configuration and more complexity to be added to supervisors, while I also > believe it belongs in the worker, as you gain a lot more flexibility. As one > additional example to what Fred said, what if you want to accumulate requests > while you wait for the connection to be established, and then issue the > commands once it is ready? There are many other considerations that are only > fully realizable in the worker.
Well, yes, in those cases you simply can't do it with delayed restarts and they are a poor fit for the case at hand ^^; I guess what I'm trying to say is... as an analogy off the top of my head, there are many list-related things you can do with lists:foldl and foldr, but you can't do _everything_ with them, and you shouldn't _try_ to do everything with them for the only reason that they exist. For some things it is simply better to use explicit recursion, some things can't be done any other way. But that is not an argument for not having foldl/foldr, is it? Kind regards, Maria _______________________________________________ eeps mailing list [email protected] http://erlang.org/mailman/listinfo/eeps
