Re: [WebDNA] HTTP Streaming -- impossible?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105540
interpreted = N
texte = You could put the result (or what you are waiting for) in a small iframe = then when the result is available it will refresh the whole page. Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 12/07/2010, at 8:58 AM, Kenneth Grome wrote: > Has anyone actually done HTTP streaming in webdna? >=20 > My understanding of the basic concept is that the server receives a = request from the browser, then it keeps the connection open via a long = running (or infinite) loop of some kind, and then it periodically pushes = new data to the outgoing stream and flushes the stream -- without = closing the connection. >=20 > I can create a loop in webdna with no problem, but how do I flush the = periodic data to the stream without the server closing the connection? = I have tried this as a test: >=20 > [loop start=3D1&end=3D10] > [waitforfile file=3DdoesNotExist.txt&timeout=3D2][/waitforfile] > [writefile textFile.txt][time][/writefile] > [include textFile.txt]
> [/loop] >=20 > ... but of course this does not work because the page is not rendered = until after the loop stops running. I get these results all at once, = but what I actually want is one line at a time pushed to the = stream/browser every 2 seconds: >=20 > 17:39:36 > 17:39:37 > 17:39:39 > 17:39:40 > 17:39:41 > 17:39:42 > 17:39:43 > 17:39:45 > 17:39:46 > 17:39:47 >=20 > I know a lot about webdna, but at the moment I cannot think of a way = to make this work. Can any of you? =20 >=20 > The problem is that webdna does not produce any results or render the = page until ALL the code on the page has been interpreted. Only then will = it send the results to the server -- which then forwards those results = on to the browser and closes the connection. >=20 > Anyone see any webdna-based alternatives here? >=20 > Sincerely, > Kenneth Grome >=20 > P.S. As an aside, my test seems to indicate that the timer in = "waitforfile" is not very accurate. The total time for all 10 lines to = be processed should have been 20 seconds, not 11. Let that be a lesson = to anyone who wants to rely on the accuracy of the waitforfile timer! >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
You could put the result (or what you are waiting for) in a small iframe = then when the result is available it will refresh the whole page. Regards Stuart Tremain IDFK Web Developments AUSTRALIA webdna@idfk.com.au On 12/07/2010, at 8:58 AM, Kenneth Grome wrote: > Has anyone actually done HTTP streaming in webdna? >=20 > My understanding of the basic concept is that the server receives a = request from the browser, then it keeps the connection open via a long = running (or infinite) loop of some kind, and then it periodically pushes = new data to the outgoing stream and flushes the stream -- without = closing the connection. >=20 > I can create a loop in webdna with no problem, but how do I flush the = periodic data to the stream without the server closing the connection? = I have tried this as a test: >=20 > [loop start=3D1&end=3D10] > [waitforfile file=3DdoesNotExist.txt&timeout=3D2][/waitforfile] > [writefile textFile.txt][time][/writefile] > [include textFile.txt]
> [/loop] >=20 > ... but of course this does not work because the page is not rendered = until after the loop stops running. I get these results all at once, = but what I actually want is one line at a time pushed to the = stream/browser every 2 seconds: >=20 > 17:39:36 > 17:39:37 > 17:39:39 > 17:39:40 > 17:39:41 > 17:39:42 > 17:39:43 > 17:39:45 > 17:39:46 > 17:39:47 >=20 > I know a lot about webdna, but at the moment I cannot think of a way = to make this work. Can any of you? =20 >=20 > The problem is that webdna does not produce any results or render the = page until ALL the code on the page has been interpreted. Only then will = it send the results to the server -- which then forwards those results = on to the browser and closes the connection. >=20 > Anyone see any webdna-based alternatives here? >=20 > Sincerely, > Kenneth Grome >=20 > P.S. As an aside, my test seems to indicate that the timer in = "waitforfile" is not very accurate. The total time for all 10 lines to = be processed should have been 20 seconds, not 11. Let that be a lesson = to anyone who wants to rely on the accuracy of the waitforfile timer! >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us
Stuart Tremain
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:
same products but different (1998)
SSL, WebSTAR, WebCatalog (1998)
[browsername] not working? (1997)
Text Variabels Not Passed To Include (2002)
Restart of DBserver (1997)
OT: passing variables to .asp (2000)
Bugs in IE 6.0 ? (2003)
Creating 404 Not Found pages (1999)
Help name our technology! (1997)
[quantity] within formulas (1997)
F3 crashing server (1997)
BUG REPORT: numeric ge, le, gr & ls comparisons don't work ... (1999)
carriage returns in data (1997)
Problems passing [SKU] with $Replace in 2.0 (1997)
Random question (1998)
WebCatalog Special <-- from SMSI (2001)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
WebCat2b13 Command Reference Doc error (1997)
problems with 2 tags (1997)
alternate location for cookies (2001)