×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From:"Dean, Robert"
That's why I really think something like Atmosphere is a better solution; it
abstracts the transport layer.The framework will negotiate that based on the
capabilities of both ends.
That may appear to be more convenient from a programming point of view. But it makes the assumption that XHR and WS are merely "transport layers" that can be used interchangeably, which may not always be true. Since XHR uses the traditional request-response cycle, the client may decide to change the next "request" based on the content of the "response", where WS just sends an acknowledgement that it received a response then continues to "listen".
This whole matter of XHR vs. WS would be settled for me if the XHR specification included an optional parameter that provided for NOT transmitting HTTP Headers in requests and responses. That way XHR would be essentially as efficient as WS, without needing to interface with a secondary WS server.
-Nathan.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
