|
|
|
|
|
by jrumbut
833 days ago
|
|
> serialised in a version of JS that the receiver understands I don't think the use case for this is as general as most RPC systems. The linked site envisions a situation where you had an app running on one server, now you want to break that workload up while making the absolute minimum number of code changes. All the clients and code would still be controlled by the same team. |
|
Using function serialisation for applicative purposes is always going to be a hack that will come back to bite the team at one time or another.