I think a picture is worth "more" than a thousand words... ;) Thanks for clearing it out - I get it now. It is still disappointing that the only way to do that is by "polling"... It's not solving the problem, just moving it around. It's fundamentally (in terms of execution-model), not different than using "long-polling" in the client instead of SSE... In both cases you got this scenario:
Side A : Are we there yet? Side B : No Side A : Are we there yet? Side B : No Side A : Are we there yet? Side B : No Side A : Are we there yet? Side B : No Side A : Are we there yet? Side B : No Side A : Are we there yet? Side B : Yes, here you go... Side A : Are we there yet? Side B : No Side A : Are we there yet? Side B : No Side A : Are we there yet? Side B : No .... The whole point of SSE is to avoid that execution model... You alluded to Redi's "push" mechanism - I've read your link on Redis's Pub/Sub protocol, but couldn't find how the push is being done. I'm currently looking into the Python-client implementation options there, but let's assume that there is a way to listen from Python to Redis - where do I put that? Inside the while-loop? And how does this "generator-instance-yield in a return statement" work from an execution-model perspective? What happens when it's sleeping? Isn't the python-run-time blocked? I mean, the controller-action "itself" is NOT a generator - it "returns" a generator-instance. It is returning an object. That object has a ".next()" method.. Great. Now what happens? Is web2py recognizing it as a generator-instance by it's type/methods ? Then it does a ".next()" call and issues the result within a response with the response headers? What happens then? It sleeps, right? What happens during that sleep? And after it finishes sleeping, it does not yield another values by itself - a generator is not a self-activating-agency - it needs to be called explicitly - only then will it replay the loop and yield another result. This part is still unclear... -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
