Re: [Proto-Scripty] Re: Progressive update messages from single request

2009-12-13 Thread Alex McAuley
- Original Message - From: joe t. thooke...@gmail.com To: Prototype script.aculo.us prototype-scriptaculous@googlegroups.com Sent: Sunday, December 13, 2009 12:49 AM Subject: [Proto-Scripty] Re: Progressive update messages from single request My crude-imentary tests are on my Win7 laptop

Re: [Proto-Scripty] Re: Progressive update messages from single request

2009-12-12 Thread Alex McAuley
: Saturday, December 12, 2009 2:24 AM Subject: [Proto-Scripty] Re: Progressive update messages from single request Alex, Thanks for the sample. i must be missing a piece somewhere though... http://pastie.org/739926 From that single Ajax.Request, the client delays, and after the PHP is done running, i get

[Proto-Scripty] Re: Progressive update messages from single request

2009-12-12 Thread joe t.
, December 12, 2009 2:24 AM Subject: [Proto-Scripty] Re: Progressive update messages from single request Alex, Thanks for the sample. i must be missing a piece somewhere though...http://pastie.org/739926 From that single Ajax.Request, the client delays, and after the PHP is done running, i

Re: [Proto-Scripty] Re: Progressive update messages from single request

2009-12-11 Thread Alex McAuley
prototype-scriptaculous@googlegroups.com Sent: Friday, December 11, 2009 1:00 AM Subject: [Proto-Scripty] Re: Progressive update messages from single request david: The buffer/flush path seems to be where this solution is heading. Don't ask me why, but iframes rub me the wrong way. With the evolving

[Proto-Scripty] Re: Progressive update messages from single request

2009-12-11 Thread joe t.
://www.thevacancymarket.com - Original Message - From: joe t. thooke...@gmail.com To: Prototype script.aculo.us prototype-scriptaculous@googlegroups.com Sent: Friday, December 11, 2009 1:00 AM Subject: [Proto-Scripty] Re: Progressive update messages from single request david: The buffer/flush path

[Proto-Scripty] Re: Progressive update messages from single request

2009-12-10 Thread david
Hi joe, I think that what you try to do could not be handle with AJAX.request (). In fact you'll receive control on a callback in the AJAX.request() when the response is complete in the browser. What you could do is a pure HTML solution: create an iFrame inside your page, and set its location to

[Proto-Scripty] Re: Progressive update messages from single request

2009-12-10 Thread david
Hi again, I'm having big finger this morning :)) so let's continue: What you could do is a pure HTML solution: create an iFrame inside your page, and set its location to the request you made, next treat this request in the server and use flush() function (in PHP) to send a part of the response.

[Proto-Scripty] Re: Progressive update messages from single request

2009-12-10 Thread T.J. Crowder
Hi Joe, It seems to me the simple way to do this is have the first request initiate a process on the server that keeps running when the request completes; the request returns an indicator of the current status and an identifier for the action. Your subsequent requests supply the identifer, which

Re: [Proto-Scripty] Re: Progressive update messages from single request

2009-12-10 Thread Alex McAuley
@googlegroups.com Sent: Thursday, December 10, 2009 8:38 AM Subject: [Proto-Scripty] Re: Progressive update messages from single request Hi Joe, It seems to me the simple way to do this is have the first request initiate a process on the server that keeps running when the request completes

[Proto-Scripty] Re: Progressive update messages from single request

2009-12-10 Thread joe t.
, December 10, 2009 8:38 AM Subject: [Proto-Scripty] Re: Progressive update messages from single request Hi Joe, It seems to me the simple way to do this is have the first request initiate a process on the server that keeps running when the request completes; the request returns an indicator

[Proto-Scripty] Re: Progressive update messages from single request

2009-12-09 Thread joe t.
Thanks for the response Walter. i can see where you're going with that, but in those successively created new Ajax.Request calls, it's generating a new request to the server, which runs the server-side routine from the beginning, right? In my concept, the first call commands the server to run all