[Seaside] Seaside 2.3 questions

[Derek Brans]

I've been inspecting 2.3 code.  I love the way it's organized in layers.

WARegistry seems to have just done away with the session cache.  Can we still have application-specific session expiration rules?

Which example seaside applications are the best examples of 2.3 - style programming?

What's the best way to do the following in 2.3
1. Insert code to determine the entry point based on the path (used to be "unhandled request")
2. pass on POST values from a non-seaside form to an entrypoint

What is a WATask?  It seems to be a controllor that encapsulates a method "go" that calls other components to render themselves.  In its rendering it does something I don't understand and uses WASimulatedRequestNotification.

I forget if there was a change in heart as to where stuff like database connection should reside for the components to access.  Was that still in the Session object?

Thank you very much,
Derek

Derek Brans
Nerd on a Wire
Web design that's anything but square
http://www.nerdonawire.com 
phone: 604.874.6463
mailto: brans at nerdonawire.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lnx-12.ams-2.theinternetone.net/pipermail/seaside/attachments/20030407/12d27655/attachment.htm