3 ms·
Without going deep into what 'functional programming' means, a remote procedure call is not necessarily functional. The use of "procedure" versus "function" in
by brudgers 10y ago
Without going deep into what 'functional programming' means, a remote procedure call is not necessarily functional. The use of "procedure" versus "function" in the name might be indicative that the remote endpoint maintains mutable state. The possibility that the remote endpoint is inaccessible indicates that the result of one call may be an (expected) integer and the result of the next call may be a (hopefully anticipated) network error.
Haskell jumps through mathematically monadic hoops to fit this class of behaviors into its functional programming paradigm. Clojure, being more practical, offers its transactional structures as a possible way of reasoning about remote calls in terms of asynchrony (a failed procedure call might be considered a process that never finishes (or not)).
Good luck.