When triggering an ajax call, the usual practice in client-side code is to create an "xmlhttp" variable and constantly check for status changes until the response is fully loaded. This creates a connection or thread between the client and server, with responses being delivered via this established link. The key difference here is that the page does not need to be refreshed. This leads to a fundamental question: Is ajax truly asynchronous?
In contrast, with JMS (Java Message Service), the request is sent without any ongoing connection between the Client and Server. Instead, the response is transmitted through a separate thread initiated by the server. This setup raises doubts about what true asynchronicity means. Can someone provide clarification on this complex issue?