Re: [WebDNA] HTTP Streaming - POSSIBLE!
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105580
interpreted = N
texte = > How about using jquery and ajax? Thanks for the link Olin, that's the kind of simple code I like! :) I think jquery may be my ultimate solution, but I have a question for you: If I switch to using jquery/ajax will the current content of my div (I'll use a div instead of an iframe) remain displayed until the new file is retrieved? Or will this content "disappear" while the jquery request is being processed? I want the previous data to remain displayed until the new data appears, so the visitor can still see the previous bid value until the new value is received from the server. As it is now, I'm using a meta-refresh tag in the page that gets loaded into the iframe. Each time this page reloads the old content of the iframe remains visible until the new iframe page has loaded. This is nice because all the visitor sees is a quick 'flash' when the new iframe page appears. The problem with this iframe solution is that the visitor also sees the browser's progress bar when the iframe is reloading, and I *think* (but I'm not sure) that using jquery will suppress this display of the browser's progress bar. This iwould be nicer from an interface perspective because having that progress bar constantly appear and disappear is an irritating distraction. > You could also update an RSS or JSON file on your server > whenever you have a change and point the jquery script > to load that up which would mean your server is not > processing the updates from the client requests but rather > serving a static file. This is what I was testing recently since I thought that a static file option might be faster than webdna. But then I learned that the static file comes up blank once in a while, which (I think) means it was served before it was completely written to disk. With so many new rewrites per second (up to 11 per second in my simulator code -- and perhaps hundreds or thousands per second at the end of a real auction) -- I think the static file option may actually be slower and/or more problematic than targeting a webdna template like I did before. Sincerely, Kenneth Grome
Associated Messages, from the most recent to the oldest:
> How about using jquery and ajax? Thanks for the link Olin, that's the kind of simple code I like! :) I think jquery may be my ultimate solution, but I have a question for you: If I switch to using jquery/ajax will the current content of my div (I'll use a div instead of an iframe) remain displayed until the new file is retrieved? Or will this content "disappear" while the jquery request is being processed? I want the previous data to remain displayed until the new data appears, so the visitor can still see the previous bid value until the new value is received from the server. As it is now, I'm using a meta-refresh tag in the page that gets loaded into the iframe. Each time this page reloads the old content of the iframe remains visible until the new iframe page has loaded. This is nice because all the visitor sees is a quick 'flash' when the new iframe page appears. The problem with this iframe solution is that the visitor also sees the browser's progress bar when the iframe is reloading, and I *think* (but I'm not sure) that using jquery will suppress this display of the browser's progress bar. This iwould be nicer from an interface perspective because having that progress bar constantly appear and disappear is an irritating distraction. > You could also update an RSS or JSON file on your server > whenever you have a change and point the jquery script > to load that up which would mean your server is not > processing the updates from the client requests but rather > serving a static file. This is what I was testing recently since I thought that a static file option might be faster than webdna. But then I learned that the static file comes up blank once in a while, which (I think) means it was served before it was completely written to disk. With so many new rewrites per second (up to 11 per second in my simulator code -- and perhaps hundreds or thousands per second at the end of a real auction) -- I think the static file option may actually be slower and/or more problematic than targeting a webdna template like I did before. 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:
[ListWords] BUG? (2003)
Help name our technology! (1997)
different show next (1997)
Disregard Not reading blanks (1998)
Re:trouble (1997)
Setting up WebCatalog with Retail Pro data (1996)
Site Search Concepts (2003)
syntax question, not in online refernce (1997)
ConvertChars request (1999)
[AppendFile] problem (WebCat2b13 Mac .acgi) (1997)
WebCat b13 CGI -shownext- (1997)
WebCat B13 Mac CGI -- Frames question (1997)
Problem with Formulas.db (1998)
WebCatalog2 for NT Beta Request (1997)
same product in cart (1997)
[addfields] bombing 5.0 (2003)
Random question (1998)
How true is this? (1999)
Calendar using WebCatalog? (1997)
ODBC problems between webcatalog and filemaker pro (2001)