Re: [WebDNA] HTTP Streaming -- impossible?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105539
interpreted = N
texte = --0016361e8806a8621f048b28341a Content-Type: text/plain; charset=ISO-8859-1 Could you use triggers somehow to get the result you need? It is specifically based on time and I remember when we were using it with authorize.net it would continuously run on a page that said processing until the response was received from authorize.net either approved or denied which then displayed the result. Sal On Sun, Jul 11, 2010 at 3:58 PM, Kenneth Grome
wrote: > Has anyone actually done HTTP streaming in webdna? > > 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. > > 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: > > [loop start=1&end=10] > [waitforfile file=doesNotExist.txt&timeout=2][/waitforfile] > [writefile textFile.txt][time][/writefile] > [include textFile.txt]
> [/loop] > > ... 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: > > 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 > > I know a lot about webdna, but at the moment I cannot think of a way to > make this work. Can any of you? > > 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. > > Anyone see any webdna-based alternatives here? > > Sincerely, > Kenneth Grome > > 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! > > --------------------------------------------------------- > 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 > --0016361e8806a8621f048b28341a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Could you use triggers somehow to get the result you need?=A0 It is specifi= cally based on time and I remember when we were using it with authorize.net it would continuously run on a page t= hat said processing until the response was received from authorize.net either approved or denied which then displ= ayed the result.
Sal
On Sun, Jul 11, 2010 at 3= :58 PM, Kenneth Grome
<kengrome@gmail.com> wrote:
Has anyone actually done HTTP streaming in webdna?
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 t= he outgoing stream and flushes the stream -- without closing the connection= .
I can create a loop in webdna with no problem, but how do I flush the perio= dic data to the stream without the server closing the connection? =A0I have= tried this as a test:
[loop start=3D1&end=3D10]
[waitforfile file=3DdoesNotExist.txt&timeout=3D2][/waitforfile]
[writefile textFile.txt][time][/writefile]
[include textFile.txt]<br>
[/loop]
... but of course this does not work because the page is not rendered until= after the loop stops running. =A0I 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:
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
I know a lot about webdna, but at the moment I cannot think of a way to mak= e this work. =A0Can any of you?
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 b= rowser and closes the connection.
Anyone see any webdna-based alternatives here?
Sincerely,
Kenneth Grome
P.S. =A0As an aside, my test seems to indicate that the timer in "wait= forfile" is not very accurate. =A0The total time for all 10 lines to b= e processed should have been 20 seconds, not 11. =A0Let that be a lesson to= anyone who wants to rely on the accuracy of the waitforfile timer!
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
--0016361e8806a8621f048b28341a--
Associated Messages, from the most recent to the oldest:
--0016361e8806a8621f048b28341a Content-Type: text/plain; charset=ISO-8859-1 Could you use triggers somehow to get the result you need? It is specifically based on time and I remember when we were using it with authorize.net it would continuously run on a page that said processing until the response was received from authorize.net either approved or denied which then displayed the result. Sal On Sun, Jul 11, 2010 at 3:58 PM, Kenneth Grome wrote: > Has anyone actually done HTTP streaming in webdna? > > 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. > > 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: > > [loop start=1&end=10] > [waitforfile file=doesNotExist.txt&timeout=2][/waitforfile] > [writefile textFile.txt][time][/writefile] > [include textFile.txt]
> [/loop] > > ... 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: > > 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 > > I know a lot about webdna, but at the moment I cannot think of a way to > make this work. Can any of you? > > 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. > > Anyone see any webdna-based alternatives here? > > Sincerely, > Kenneth Grome > > 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! > > --------------------------------------------------------- > 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 > --0016361e8806a8621f048b28341a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Could you use triggers somehow to get the result you need?=A0 It is specifi= cally based on time and I remember when we were using it with authorize.net it would continuously run on a page t= hat said processing until the response was received from authorize.net either approved or denied which then displ= ayed the result.
Sal
On Sun, Jul 11, 2010 at 3= :58 PM, Kenneth Grome
<kengrome@gmail.com> wrote:
Has anyone actually done HTTP streaming in webdna?
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 t= he outgoing stream and flushes the stream -- without closing the connection= .
I can create a loop in webdna with no problem, but how do I flush the perio= dic data to the stream without the server closing the connection? =A0I have= tried this as a test:
[loop start=3D1&end=3D10]
[waitforfile file=3DdoesNotExist.txt&timeout=3D2][/waitforfile]
[writefile textFile.txt][time][/writefile]
[include textFile.txt]<br>
[/loop]
... but of course this does not work because the page is not rendered until= after the loop stops running. =A0I 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:
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
I know a lot about webdna, but at the moment I cannot think of a way to mak= e this work. =A0Can any of you?
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 b= rowser and closes the connection.
Anyone see any webdna-based alternatives here?
Sincerely,
Kenneth Grome
P.S. =A0As an aside, my test seems to indicate that the timer in "wait= forfile" is not very accurate. =A0The total time for all 10 lines to b= e processed should have been 20 seconds, not 11. =A0Let that be a lesson to= anyone who wants to rely on the accuracy of the waitforfile timer!
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
--0016361e8806a8621f048b28341a--
sal danna
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:
Not really WebCat- (1997)
OSX (2002)
Problems appending to database (1997)
problems with 2 tags (1997)
[WebDNA] Adding Graphics to Directory (2009)
Re:slowness (1998)
fieldType=num (1997)
PIXO (1997)
Exclamation point (1997)
WebCatalog 2.0 b 15 mac (1997)
How to Sort Summ data ? (1997)
WebCatalog can't find database (1997)
% (mod) was looping table rows (1999)
orders being printed (1998)
bug in [SendMail] (1997)
WCS Newbie question (1997)
Summary search -- speed (1997)
Linked lists and Recursive searching (2003)
WC2b12: Yes, Formulas.db is for real (1997)
retain raw [cart] submitted value (2004)