Are the things you are seeing just normal activity with any TCP/IP
socket connection?
I used a filter in Wireshark to filter out any traffic that was not specifically between my browser and
http://jwebsocket.org
Filter: ip.dst == 83.169.11.55
Without a filter, it is shocking to see all the traffic that gets generated; some of which may be attributed to spyware that most of us download over the Internet.
No, I specifically compared the bytes transferred by the jwebsocket chat service to the service on my IBM i system, which uses XHR and simulate 4 chat clients.
http://www.radile.com/rdweb/temp/meet.html
With respect, maybe you are getting too bogged down
in the detail.
Well, okay. But I have an interest in meeting and broadcast services under HTTP and I want to know if Web Sockets is better than XHR.
With my web socket alternative, there is virtually no latency - ever.
You should try the chat simulator on my Web site. Persistent connections. No latency. No iterative polling. If I were implementing a CTI application like yours, I'd probably use the same technique.
So while waiting for a call, my browser is flooding the server with 600 HTTP requests per second.
I understand. That would be ridiculous. But I see a lot of that on the Internet.
-Nathan.
As an Amazon Associate we earn from qualifying purchases.
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.