27 Jan
2012
27 Jan
'12
3:26 p.m.
Hi Lukas,
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've posted on the
Seaside-dev list - using a cookie enabled WACounter as the example.
There is one issue that could simplify things in the meantime:
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't work properly in that situation either. By
adding PRContext as a session property PRContextFilter wouldn't be
necessary and the code simplified.
Nick
* If however
we want to allow for multiple components so that state isn't
maintained between two identical Restful - that is both counters start
at 0.
Then we could move PRContext into the session,
and remove the
PRContextFilter.
All components should preserve their state across their session. Also
I would try to avoid depending on a specific WASession, that was a big
problem in Pier 1 because you could not easily use it in your own
application (for example as a help or documentation system).