launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #04445
Re: optimizing adding team members
On Tue, Aug 10, 2010 at 7:55 PM, Robert Collins
<robert.collins@xxxxxxxxxxxxx> wrote:
> >From our end, I'd love that to look like this:
> - we receive a request
> - we commit the *intent*, dispatch to a queue
> - the request puts itself into long-poll mode
> - the queue processes the work
> - the queue callsback the appserver which reactivates the request
> which then delivers the users response
>
> Thats going to need some serious plumbing, a rearrangement of /all/
> the global-request-specific-state and so on. Not on the cards for now.
Only if implemented in the way you describe above. What we do in
Landscape goes as follows:
- we receive a request
- we commit the *intent*, dispatch to a queue, generate a page identifier
- we deliver the response back to the user, basically a page with a spinner
- a new (XHR) request is fired, in long-poll mode, with the page identifier
- the queue processes the work
- the queue notifies that it's done, making the long-poll request
return and delivering the response
-- Sidnei
Follow ups
References