This operating schema continues to use and abide by the HTTP protocol and the client-driven request/response model. The client is always the one to take the initiative, deciding when to connect to the server.
However, there are scenarios where HTTP is not very efficient. With this protocol it is not easy to implement instant-messaging applications or chat-rooms, collaboration tools, multiuser online games or real-time information services, even when using asynchrony.
The reason is simple: HTTP is not oriented to real time. There are other protocols, such as the popular IRC, which are indeed focused on achieving swifter communication in order to offer more dynamic and interactive services than the ones we can obtain using Pull. In them, the server can take the initiative and send information to the client at any time, without waiting for it to request it expressly.
This operating schema continues to use and abide by the HTTP protocol and the client-driven request/response model. The client is always the one to take the initiative, deciding when to connect to the server.However, there are scenarios where HTTP is not very efficient. With this protocol it is not easy to implement instant-messaging applications or chat-rooms, collaboration tools, multiuser online games or real-time information services, even when using asynchrony.The reason is simple: HTTP is not oriented to real time. There are other protocols, such as the popular IRC, which are indeed focused on achieving swifter communication in order to offer more dynamic and interactive services than the ones we can obtain using Pull. In them, the server can take the initiative and send information to the client at any time, without waiting for it to request it expressly.
การแปล กรุณารอสักครู่..