Re: [WebDNA] Dynamic server feedback?
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 103788
interpreted = N
texte = > No loop, that's the javascript (AJAX). Okay, let's say the browser sends a request to a webdna page so webdna does a search. When this happens webdna returns the current results of the search immediately -- but it does not search again automatically in order to update these results ... So in order to update the search results dynamically in the browser, the AJAX Javascript repeats the original request to the server -- perhaps on a timed basis, and apparently over the original connection which is held open by the XMLHTTPRequest object -- and then Javascript displays the new results in the browser "dynamically" so that the page itself does not have to be reloaded. If this is how it works then webdna is still doing a lot of repeated searches! It's just that the Javascript is making these requests automatically, rather than the visitor clicking a link or form button to get the new results manually. ------- I guess a similar effect might be obtained by putting a meta-refresh tag into a webdna template that's loaded into an iframe. This would effectively repeat the request on a timed basis, sort of like the Javascript does via XMLHTTPRequest. Naturally this approach would result in more server overhead because each of these iframe requests would open and close a new connection -- unlike the XMLHTTPRequest which repeats its requests over the original connection. But if the server is fast enough to handle these repeated requests the end result would look the same to the visitor, correct? Sincerely, Ken Grome
Associated Messages, from the most recent to the oldest:
> No loop, that's the javascript (AJAX). Okay, let's say the browser sends a request to a webdna page so webdna does a search. When this happens webdna returns the current results of the search immediately -- but it does not search again automatically in order to update these results ... So in order to update the search results dynamically in the browser, the AJAX Javascript repeats the original request to the server -- perhaps on a timed basis, and apparently over the original connection which is held open by the XMLHTTPRequest object -- and then Javascript displays the new results in the browser "dynamically" so that the page itself does not have to be reloaded. If this is how it works then webdna is still doing a lot of repeated searches! It's just that the Javascript is making these requests automatically, rather than the visitor clicking a link or form button to get the new results manually. ------- I guess a similar effect might be obtained by putting a meta-refresh tag into a webdna template that's loaded into an iframe. This would effectively repeat the request on a timed basis, sort of like the Javascript does via XMLHTTPRequest. Naturally this approach would result in more server overhead because each of these iframe requests would open and close a new connection -- unlike the XMLHTTPRequest which repeats its requests over the original connection. But if the server is fast enough to handle these repeated requests the end result would look the same to the visitor, correct? Sincerely, Ken 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:
WebCat2 - [include] tags (1997)
.htaccess to make WebDNA serve HTML (2007)
Re1000001: Setting up shop (1997)
How much is too much? I can never remember the answer. (2002)
[WebDNA] PayPal Instant Payment Notification Guide (2009)
I can help! (1996)
Cut off from the list and can't get an answer to the confused re:QTY price updating question (1998)
removing programming logic white space (2003)
Country & Ship-to address & other fields ? (1997)
Regarding PayPal (was Payments -> Bank Accounts) (2005)
ReturnRaw context (1997)
Re:Virtual hosting and webcatNT (1997)
possible, WebCat2.0 and checkboxes-restated (1997)
encrypting without "ugly" URLs (2005)
Help need to figure this out today!!! Advanced Question. (2004)
re:WebCatalog and Filemaker (1996)
Version f1 status (1997)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
WebCat2b15MacPlugin - showing [math] (1997)
WebCat2b12 - nesting [tags] (1997)