3 ms·
How pedantic do you want to be about it? I'm sure people will tell you "No, that's not true FFI." It's close enough, if you generalize REST to a sort of RPC wh
by gavinray 5y ago
How pedantic do you want to be about it?
I'm sure people will tell you "No, that's not true FFI."
It's close enough, if you generalize REST to a sort of RPC where HTTP is the transport/protocol.
There are problems you run into when you use "true" FFI -- namely ABI/binary compatibility (you're beholden to compiler or OS behaviors) and the fact that non-native languages can't directly communicate with you.
Doing something over the network has a performance penalty, and there's marshalling costs involved.
But IMO, if you expose an IPC or socket-based API (rather than a C ABI) I'm not sure very many people could fault you.