![]() This is very inefficient but a very simple way to achieve real-time behavior. Otherwise, no information will be sent to the client and the client will again make a new connection after sometime. If the server has new information available it will send back data in the response. With polling, the client makes synchronous calls to get information from the server. Some of these workarounds are polling, long polling, and streaming. Developers have created some workarounds or hacks to overcome this HTTP shortcoming. A Walkie-talkie is an example of a half duplex device because only one person can speak at a time. ![]() HTTP was designed to be half-duplex which means it allows transmission of data in just one direction at a time. Persistent connections allowed web browsers to reuse the same connection for fetching images, scripts, etc. This was improved in HTTP 1.1 with the introduction of HTTP persistence connections. To learn how to use Wildfly with OpenShift please refer to my second post in this series /deploy-websocket-web-applications-with-jboss-wildflyīefore the HTTP 1.1 version, every request made to the server resulted in a new connection. HTTP is bit chatty in nature, as for each http request/response, a lot of headers need to be transmitted over the wire. HTTP was designed for document sharing and not for building today's highly interactive web applications. This simple design of the HTTP protocol makes it very scalable but inefficient and unsuitable for highly interactive real-time web applications. It is a well known fact that HTTP(Hypertext Transfer Protocol) is a stateless request-response protocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |