Meaning?

Post #9,496 by admin 9/17/01 3:36:42 PM 9/17/01 3:40:22 PM Reply	Meaning? Does mime/multipart get rid of the spinner problem? It might solve another issue we have too... an ever-growing document uses up more and more memory, even if you delete the script elements through the DOM. Regards, -scott anderson Edited by admin Sept. 17, 2001, 03:40:22 PM EDT Expand All History
Post #9,508 by ben_tilly 9/17/01 4:35:55 PM Reply	I thought it did but... on closer investigation I didn't see how to do it for IE. :-( OTOH you can use a client pull as well. Just have the frame replace itself every 1000 miliseconds. Be sure each time to pass in the old, "Maximum known update counter", and just send back all new known updates, and you will be sending a series of small, independent documents. Furthermore if you do it with a replace (or whatever the meta equivalent is) then you won't generate those annoying history items. Cheers, Ben
Post #9,511 by admin 9/17/01 4:52:50 PM Reply	The object is to avoid opening a connection every second. We'll be supporting several thousand clients, all receiving realtime updates to their browsers at a rate of 6-40 per second. Regards, -scott anderson
Post #12,440 by tablizer 10/9/01 12:43:51 PM Reply	40 per second? Faster than a MOVIE >> We'll be supporting several thousand clients, all receiving realtime updates to their browsers at a rate of 6-40 per second. << Do you mean that the data changes up to 40 times per second, or that the users screen has to change 40 times per second? That is faster than most movie refresh rates, and movies are usually buffered and not customized per user. Hell of a requirement. I suggest you look into missle guidence techniques or something. You are gonna need high-end stuff. I doubt off-the-shelf browsers can cut it. ________________ oop.ismad.com
Post #12,456 by admin 10/9/01 2:17:19 PM Reply	Re: 40 per second? Faster than a MOVIE 40 fields updating per second. This equates to approximately 6-12 line items updating per second. And yes, the user's screen has to change as the events occur. Hell of a requirement, but easily satisfied with 2 days of Javascript/DOM coding, and it runs in IE 5, IE 5.5, Netscape 6, and Mozilla with no browser-specific code. Once again, just because your tiny little realm of experience and knowledge can't conceive of a simple solution that doesn't require inventing your own Tablizer-brand[tm] way of doing things, doesn't mean that such a solution doesn't exist. Regards, -scott anderson
Post #14,576 by addison 10/22/01 12:59:40 PM Reply	From the mouth of.. erm.. babes. 40 fields updating per second. This equates to approximately 6-12 line items updating per second. And yes, the user's screen has to change as the events occur. He's onto something with his movie comparison. Shoulda just done it in Flash, and sent new screenshots as it changes. :) muahaahahahahaha. :) (running away now) Addison

Welcome to IWETHEY!