Thanks all. I've looked at the MSeven solution and other consoles but was looking something more interactive.
Basically a user selects a job that processes N tasks. Right now the 'waiting' message sits there and the user is unaware of where in 1..N they are. I have not succeeded in showing each of these N tasks being run using the ob_flush technique inside of CakePHP. I thought that if I passed the N tasks to the view and let the Javascript in the view run each of those N jobs using Ajax that I would be able to give user more indication of where in 1..N they are. I thought this was so simple that I was either missing something huge or I was reinventing the wheel. On Jan 5, 10:02 pm, Geoff Douglas <drdouglas...@gmail.com> wrote: > This is a limitation of the web in general isn't it? > > In the web development world, each request is a unique call to the > server... so there is no such thing as "progress." You request something, > and the server responds. Even in the case where you pass over the > processing to a daemon of some kind, you still must repeatedly request the > status of that worker process, by individual web requests. > > If you use an java applet or something of that nature, than you can get > that kind of feedback, but then you are no longer using web requests, or > even a web server. The connection necessary for this type of real time, > progress feedback requires a persistent connection to the server, generally > this traffic is handled via a different protocol altogether. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
