Re: [WebDNA] HTTP Streaming - POSSIBLE!
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105567
interpreted = N
texte = > Which included a script that reloaded itself > upon the creation of the next sequential file. I already have a mockup of my auction site working with a simple meta-refresh in an iframe, so I don't see how your approach is going to solve any problems for me. The problems I am anticipating are latency and overhead. Maybe I can get rid of some of that with XMLHTTPRequest, but I don't think it's going to help much, because even though Javascript can be programmed to open a new server connection via XMLHTTPRequest as soon as the last one closes, the browser still has to repetitively open and close these connections -- every second or two at a minimum if I'm hoping to keep the browsers updated with the most recent bid price. Unfortunately this polling must be initiated by the browser, not by the server, and this means as many as a couple thousand connections per second -- just to CHECK to see if the data has been updated. If the data has not been updated then it's a wasted connection because the connection still has to be opened, then the current data sent (again), then the connection closed. A better alternative might be to "keep the connection open" and send each update to the browser as it happens, over the same open connection. This gets rid of the latency inherent in polling once each second because the data gets sent immediately instead of waiting to be sent upon the next polling request ... and it gets rid of most of the overhead inherent in building up and tearing down all those connections. Unfortunately webdna is not appropriate for this type of application, so I've come up with a work-around meta-refresh / iframe technique as a possible alternative. It's not the best alternative, that's for sure, but it's a potential solution that I can understand. I only hope that webdna is fast enough to respond to all those connections. Or I hope to find a better alternative ... Sincerely, Kenneth Grome
Associated Messages, from the most recent to the oldest:
> Which included a script that reloaded itself > upon the creation of the next sequential file. I already have a mockup of my auction site working with a simple meta-refresh in an iframe, so I don't see how your approach is going to solve any problems for me. The problems I am anticipating are latency and overhead. Maybe I can get rid of some of that with XMLHTTPRequest, but I don't think it's going to help much, because even though Javascript can be programmed to open a new server connection via XMLHTTPRequest as soon as the last one closes, the browser still has to repetitively open and close these connections -- every second or two at a minimum if I'm hoping to keep the browsers updated with the most recent bid price. Unfortunately this polling must be initiated by the browser, not by the server, and this means as many as a couple thousand connections per second -- just to CHECK to see if the data has been updated. If the data has not been updated then it's a wasted connection because the connection still has to be opened, then the current data sent (again), then the connection closed. A better alternative might be to "keep the connection open" and send each update to the browser as it happens, over the same open connection. This gets rid of the latency inherent in polling once each second because the data gets sent immediately instead of waiting to be sent upon the next polling request ... and it gets rid of most of the overhead inherent in building up and tearing down all those connections. Unfortunately webdna is not appropriate for this type of application, so I've come up with a work-around meta-refresh / iframe technique as a possible alternative. It's not the best alternative, that's for sure, but it's a potential solution that I can understand. I only hope that webdna is fast enough to respond to all those connections. Or I hope to find a better alternative ... Sincerely, Kenneth Grome
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
TCPConnect (2002)
using showpage and showcart commands (1996)
[quantity] solved (1997)
Is everybody getting all the posts? (2002)
serial number dishing (1997)
Requiring that certain fields be completed (1997)
Location of Browser Info.txt file (1997)
DNS Name lookup (1998)
Field validation problem (1999)
Dividers (2003)
Sendmail - Pick Mail Server (2004)
email error (2003)
WebCat2b15MacPlugin - showing [math] (1997)
Re:Help name our technology! (1997)
Multiple Pulldowns (1997)
NumFound (1999)
Protect vs Authenicate (1997)
Filemaker Pro Template for Orders (1999)
TaxTotal Problem (1997)
Protect and Serve (1999)