On Tue, Jan 31, 2012 at 8:14 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com" target="_blank">philippe.marschall@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/1/31 Nick Ager <<a href="mailto:nick.ager@gmail.com">nick.ager@gmail.com</a>>:<br>
<div class="im">> However, the point I tried to make above is that this is a general Seaside</div><div class="im">
> problem - not specific to Pier, though Pier as a RESTful application exposes<br>
> the issue.<br>
<br>
</div>Right. But my understanding is that from what Julian said there is no<br>
generic fix because if you don't have a RESTful (probably the wrong<br>
word) URL then the current behavior is correct. To me the problem<br>
seems to be that we hack all these things into #initialRequest:<br>
because that's the only real way we have of dealing with state in the<br>
URL. To me the question is whether instead of putting another brittle<br>
hack into WASession we should rather move things that don't really<br>
need a session into a filter on session or application and have a<br>
better way to initialize components from state from the request URL.<br>
In general better support for applications that have state in the URL.<br>
This kinda goes in the way of the "Window shopping mode" that David<br>
Buck was talking about. A generic way of going form a session less<br>
application to a session based application. You recently said you<br>
wanted vision, there it is :-)<br><br></blockquote><div>I've been playing this week again with pulling the concept of a session (i.e. what the rest of the world calls a session) up outside the level of the Application. This means you could wrap the entire site (or a particular Dispatcher) in a session filter that would make the session available to everything below it. This seems to work pretty well (need to sort out how to deal with query-parameter-based session keys, but works fine with cookies...) and seems like it ought to make such a transition easier.</div>
<div><br></div><div>Still experimenting with ideas... (that's only one of many on the go in this image)</div><div><br></div><div>Julian</div></div><br>