Re: [WebDNA] HTTP Streaming -- impossible?

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105556
interpreted = N
texte = On Jul 12, 2010, at 2:18 PM, Kenneth Grome wrote: >> I just ran a test, and entering all asterisks in the timer fields, >> including the "Second" field, results in a trigger that executes >> every second. Give it a try. > > Thanks for the test Brian, I should have thought of that. The > instructions are wrong in this case, but at least it makes my > trigger management easier ... :) > > >> If you had a trigger that ran once per second and wrote the auction >> status to a text or xml file, you could use XMLHttpRequest (AJAX) >> to fetch that file from the client page and update the page content >> with the results. This would execute very fast, and not bother >> WebDNA with every client request, just with the once-per-second >> trigger. > > I was working on this approach a year ago or so on another website, > but the project ended prematurely so I never learned how this works, > and that's why I'm going to ask: > > How does the XMLHTTPRequest know when the file has changed on the > server? It needs to know this so it can download the new and > updated file, right? no, I think you just grab it as often as it *could* have changed. If it has not changed then you don't have to update the facade with the new (same old) data. ------------ Govinda govinda.webdnatalk@gmail.com Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  2. Re: [WebDNA] HTTP Streaming -- impossible? (christophe.billiottet@webdna.us 2010)
  3. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  4. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  5. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  6. Re: [WebDNA] HTTP Streaming -- impossible? (Govinda 2010)
  7. Re: [WebDNA] HTTP Streaming -- impossible? (sal danna 2010)
  8. Re: [WebDNA] HTTP Streaming -- impossible? (Jesse Proudman 2010)
  9. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  10. Re: [WebDNA] HTTP Streaming -- impossible? (Jesse Proudman 2010)
  11. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  12. Re: [WebDNA] HTTP Streaming -- impossible? (Govinda 2010)
  13. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  14. Re: [WebDNA] HTTP Streaming -- impossible? (Brian Fries 2010)
  15. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  16. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  17. Re: [WebDNA] HTTP Streaming -- impossible? (Marc Thompson 2010)
  18. Re: [WebDNA] HTTP Streaming -- impossible? (sal danna 2010)
  19. Re: [WebDNA] HTTP Streaming -- impossible? (Lawrence 2010)
  20. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  21. Re: [WebDNA] HTTP Streaming -- impossible? (Stuart Tremain 2010)
  22. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  23. Re: [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
  24. Re: [WebDNA] HTTP Streaming -- impossible? (Stuart Tremain 2010)
  25. Re: [WebDNA] HTTP Streaming -- impossible? (sal danna 2010)
  26. [WebDNA] HTTP Streaming -- impossible? (Kenneth Grome 2010)
On Jul 12, 2010, at 2:18 PM, Kenneth Grome wrote: >> I just ran a test, and entering all asterisks in the timer fields, >> including the "Second" field, results in a trigger that executes >> every second. Give it a try. > > Thanks for the test Brian, I should have thought of that. The > instructions are wrong in this case, but at least it makes my > trigger management easier ... :) > > >> If you had a trigger that ran once per second and wrote the auction >> status to a text or xml file, you could use XMLHttpRequest (AJAX) >> to fetch that file from the client page and update the page content >> with the results. This would execute very fast, and not bother >> WebDNA with every client request, just with the once-per-second >> trigger. > > I was working on this approach a year ago or so on another website, > but the project ended prematurely so I never learned how this works, > and that's why I'm going to ask: > > How does the XMLHTTPRequest know when the file has changed on the > server? It needs to know this so it can download the new and > updated file, right? no, I think you just grab it as often as it *could* have changed. If it has not changed then you don't have to update the facade with the new (same old) data. ------------ Govinda govinda.webdnatalk@gmail.com Govinda

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:

A quickie question (1997) Displaying raw values (long) (1998) Loosing Quantity (2000) date pref (1999) Sendmail truncation in Eudora Clients (1998) RE: Symantec VIsual Page 1.0.3 (1997) ACGI processing for .html (1997) WebCat2 - Getting to the browser's username/password data (1997) Searching multiple fields (1997) Cart Number sequence (1997) WCS Newbie question (1997) SMTP Mail Server (2003) how many users (2000) Summing fields (1997) Need help with text area (1998) Enhanced Master Counter? (1997) [OT] - CSS Based Layout and Design (2004) RE: WebCatalog2 for NT Beta Request (1997) [ShowIf] and empty fields (1997) extending webcatalog (1997)