tag:blogger.com,1999:blog-5196103582241137578.post5002167867781315738..comments2024-03-08T10:52:16.816+01:00Comments on eneter.net: How to Design Interprocess CommunicationOndrejhttp://www.blogger.com/profile/11029096061173289386noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-5196103582241137578.post-39814576356176230782013-07-05T22:32:47.132+02:002013-07-05T22:32:47.132+02:00Nice article Ondrej. Just a few comments:
TCP and...Nice article Ondrej. Just a few comments:<br /><br />TCP and HTTP are actually on two different layers (resp. transport and application) and TCP is actually the most common transport layer protocol used with HTTP. Also HTTP doesn't prevent having both system connect to each other and send messages in both direction. The tricks you mention are only necessary if only one system (e.g. a client) can connect to the other one (e.g. server) but not the other way around. Of course as you mention, Websockets have the advantage that they allow the server to send messages to the client even though the connection has been opened by the client (which requires tricks to work with HTTP).Henrihttp://benohead.comnoreply@blogger.com