On Thu, Oct 4, 2012 at 3:18 PM, Massimo Lusetti <[email protected]> wrote: > On Thu, Oct 4, 2012 at 9:04 PM, Howard Lewis Ship <[email protected]> wrote: > >> Users will want to configure their private pass phrase using a newly >> defined symbol. If left unconfigured, there will be a runtime error >> logged (not an exception, just an error to encourage users to select a >> private pass phrase). > > Why not generate a random string if not supplied. > Doesn't it work better then the "DEFAULT" string?
That would not work in a cluster; different servers in the cluster would not be able to read each other's streams. Yes, usually, its based on sticky sessions, but even then, there's fail-over to consider. Also, a server restart would not only lose client sessions, but would generate a new random key, so any forms would become unsubmittable even if they did not depend on server-side session state. > > It could lowered the error to a warning too. To be honest, in a perfect world, it would blow up with an exception ... but that's too draconian, especially for something added this late in the game. Warnings are completely ignored. I'm even tempted to add a message to the AlertManager service, to really get it in front of the developer's eyes, pronto. > > -- > Massimo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
