This is probably a gross oversimplification, but are internet website read/write requests basically MPI-like?
EggyLv999
Not quite. There's obviously a lot of differences, but one of the big ones is that a server is constantly ready to receive requests, and the client makes a request which the server responds to, while MPI is for point-to-point one way communication, ie there is no request/response just a message passed through the exchange.
ant
I too agree that they aren't similar, but I believe that the comparison doesn't really make sense.
If by website read/write requests we're referring to HTTP GET/POST requests, then the two are abstractions built for totally different purposes. In fact, a majority of abstractions that deal with communication over networks will appear similar, because they rely on similar underlying OS primitives.
This is probably a gross oversimplification, but are internet website read/write requests basically MPI-like?
Not quite. There's obviously a lot of differences, but one of the big ones is that a server is constantly ready to receive requests, and the client makes a request which the server responds to, while MPI is for point-to-point one way communication, ie there is no request/response just a message passed through the exchange.
I too agree that they aren't similar, but I believe that the comparison doesn't really make sense.
If by website read/write requests we're referring to HTTP GET/POST requests, then the two are abstractions built for totally different purposes. In fact, a majority of abstractions that deal with communication over networks will appear similar, because they rely on similar underlying OS primitives.