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 allows the server- side page to check the progress of the ongoing work matching that ID and report back the (new) status. People use things like this for showing progress bars for file uploads without using Flash, that kind of thing. HTH, -- T.J. Crowder Independent Software Consultant tj / crowder software / com www.crowdersoftware.com On Dec 9, 4:11 pm, "joe t." <[email protected]> wrote: > i think i've seen examples of this, but can't recall where, and could > use some guidance. > > Obviously it's easy to handle a 1:1 Request/Response > > How can i do a true 1:many process? For instance: > Client takes a single action which requires the server to perform 3 > tasks: > * Query database > * Generate PDF > * Generate email, attach PDF, and send > > How can i respond to the client as EACH task is accomplished without > ending the request chain? > "Looking up your data . . ." (time-based dots as delay indicator) > "Creating PDF . . ." > "Email sent" (or failed, as the case may be) > > Is this done with HTTP 2xx headers? Recursive callbacks? If anyone can > point me in the right direction (which include samples), i'd be > grateful. > > Thanks. > -joe t. -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
