<div class="gmail_quote">On Mon, May 14, 2012 at 9:00 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com" target="_blank">philippe.marschall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, May 14, 2012 at 8:30 PM, Julian Fitzell <<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>> wrote:<br>
> I can't tell for sure, but this *sounds* like it's related to work I was<br>
> playing with at ESUG last year. There were two parts:<br>
> 1) Making session continuations into request handlers. This is implemented<br>
> in the 3.1 repository. A new render loop can thus be easily started by<br>
> creating a new request handler and delegating to it or registering it in a<br>
> dispatcher or registry.<br>
<br>
</div>I though about that too. But I haven't yet figured out the details.<br>
Should it be an application, a registry or something else? In which<br>
object should the request hander cache be an in which the REST<br>
methods? I guess we should experiment.<br>
<br>
Also, I'm a bit worried about our senders of #application :-(<br></blockquote><div><br></div><div>How so? (apologies, the details of the change are fuzzy at the moment, but I thought the impacts were pretty minor)</div>
</div>