Re: [WebDNA] Dynamic server feedback?
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 103791
interpreted = N
texte = We are actively working on the fastCGI version of WebDNA ;-) - chris On Oct 16, 2009, at 9:02, Kenneth Grome wrote: >> Perhaps they pull down many at once >> and update client side for effect. > > No, they do it all live and in real time, I've seen the evidence > myself. I also know there are special servers for this type of > system. The stock ticker websites are driven by them, I think they > are called "Comet" servers if I'm not mistaken. > > I want to do something similar to the swoopo site but I just want to > use a normal web server with webdna -- on a much smaller scale of > course. > > I wish webdna worked with the nginx web server because nginx is > reported to be a blazing fast server compared with Apache and nearly > all other web servers in use these days. But webdna does not > support FastCGI so I doubt that this combination is going to be an > option any time soon. > > Sincerely, > Ken Grome > > > >> >> >> On Oct 16, 2009, at 5:48 AM, Kenneth Grome
>> wrote: >> >>>> 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 >>> >>> >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> old archives: http://dev.webdna.us/TalkListArchive/ >>> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> old archives: http://dev.webdna.us/TalkListArchive/ >> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 >> > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288
Associated Messages, from the most recent to the oldest:
We are actively working on the fastCGI version of WebDNA ;-) - chris On Oct 16, 2009, at 9:02, Kenneth Grome wrote: >> Perhaps they pull down many at once >> and update client side for effect. > > No, they do it all live and in real time, I've seen the evidence > myself. I also know there are special servers for this type of > system. The stock ticker websites are driven by them, I think they > are called "Comet" servers if I'm not mistaken. > > I want to do something similar to the swoopo site but I just want to > use a normal web server with webdna -- on a much smaller scale of > course. > > I wish webdna worked with the nginx web server because nginx is > reported to be a blazing fast server compared with Apache and nearly > all other web servers in use these days. But webdna does not > support FastCGI so I doubt that this combination is going to be an > option any time soon. > > Sincerely, > Ken Grome > > > >> >> >> On Oct 16, 2009, at 5:48 AM, Kenneth Grome >> wrote: >> >>>> 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 >>> >>> >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> old archives: http://dev.webdna.us/TalkListArchive/ >>> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> old archives: http://dev.webdna.us/TalkListArchive/ >> Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288 >> > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > Bug Reporting: http://forum.webdna.us/eucabb.html?page=topics&category=288
christophe.billiottet@webdna.us
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:
webmerchant 3.0 questions (1999)
calculate user's age (1999)
[WebDNA] [TEXT] limit (2019)
BUG in WebCatalog 4.0.1 on Mac OSX (2000)
Prices coming up 0.00 (2001)
WC2.0 Memory Requirements (1997)
SiteBuilder? - SlideShow (2004)
Shop till you drop dead on the avenue ... (1997)
problems with 2 tags (1997)
Pithy questions on webcommerce & siteedit (1997)
Shipping based in distance and weight (1999)
Snake Bites (1997)
File info on files with funky characters in their names (2003)
Re[2]: HELP: OS X Problem... (2000)
WebDNA Challenge - Was: Why WebDNA is not popular (2002)
createfolder not behaving as expected (1999)
[WebDNA] PROBLEM WITH [SQL] (2009)
headers in webcat 4.0. (2000)
shipcost - cleaner with a table (1998)
[protect] on NT? (1997)