3 ms·
In REST terminology, there's nothing particular special about a "client" or a "server". Clients make requests, servers respond. There's nothing to stop the "se
by rswail 5y ago
In REST terminology, there's nothing particular special about a "client" or a "server". Clients make requests, servers respond.
There's nothing to stop the "server" connecting to the "client" and making requests to it to "push" data.
REST as a style is not particularly well suited to streams of data, which is what web sockets sort of solve in an unstructured way.