I would do this with chained onSuccess handlers. Each one would
trigger a new request to a different endpoint, carrying some token to
identify the visitor.
//do your lookup
//make your pdf
onCreate:..., //you get the idea
On Dec 9, 2009, at 11:11 AM, joe t. 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
> * 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
> -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@example.com
> To unsubscribe from this group, send email to
> For more options, visit this group at
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 prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at