From: Jack Kingsley
Nathan, this is pretty nice, how many users do you envsion using
this at the same time.
When you ask about "this", I hope you're not referring to the application, which is just a proof of concept, representing 4 chat participants in 1 meeting by using 4 inline frames.
However, I envision an IBM i server scaling to thousands of concurrent meeting participants. Broadcasting a "message" takes something less than 2 milliseconds of CPU time per participant. So a 4-core server may max out at something like 3,000 messages per second. Actually, I'm not sure that CPU would be the bottleneck.
I typed test in each window where it came back to all 4
windows and I did it from each different color
That's right. Each color represents an individual meeting participant.
it showed me that no matter where you typed all users could see
it based on where I typed it from.
I'm glad that was understood. A clever JavaScript programmer could update each of the 4 inline frames without posting a message to the server, but part of proving the concept is having the server actually broadcast the message simultaneously to all participants.
Thanks for the feedback.
-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.