Hi Lukas,<div><br></div><div>Thanks for the reply. Looking again at the issues they are more Seaside bugs than Pier bugs. Or rather the Seaside bugs should be resolved first, then any outstanding Pier bugs can be addressed. I&#39;ve posted on the Seaside-dev list - using a cookie enabled WACounter as the example. </div>
<div><br></div><div>There is one issue that could simplify things in the meantime:</div><div><br></div><div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
&gt; * If however we want to allow for multiple components so that state isn&#39;t<br>
&gt; maintained between two identical Restful - that is both counters start at 0.<br>
&gt; Then we could move PRContext into the session, and remove the<br>
&gt; PRContextFilter.<br>
<br>
</div>All components should preserve their state across their session. Also<br>
I would try to avoid depending on a specific WASession, that was a big<br>
problem in Pier 1 because you could not easily use it in your own<br>
application (for example as a help or documentation system).<br></blockquote><div><br></div><div><span class="Apple-style-span">PRContext could be stored in a WASession property and still allow Pier to be used by Seaside apps. Storing in a session property would prevent two or more Pier instances being used within a Seaside app - although the current PRContextFilter won&#39;t work properly in that situation either. By adding PRContext as a session property </span>PRContextFilter<span class="Apple-style-span"> wouldn&#39;t be necessary and the code simplified.</span></div>
<div><br></div><div>Nick</div></div></div></div>