6 ms·
One pro of HTTP is that the methods are barebones and error codes standardized, while there are plenty of battle tested front ends for your tx/rx endpoints that
by unlinked_dll 7y ago
One pro of HTTP is that the methods are barebones and error codes standardized, while there are plenty of battle tested front ends for your tx/rx endpoints that might touch the service. Basically works everywhere.
The con is that you can do that with the protocol of your choice directly and you don't need to bolt HTTP to whatever you're building.