I have run into the same problem. Does someone from the Tapestry dev team has any suggestion about the best value for this (now mandatory) field?
Also if we put the value to be random as suggested above is it not possible that 2 application that run on different hosts and thus will generate it differently will not be able to be interchangeable? In other words the application A wont be able to handle to request made to application B however the cluster will still send it cheers -- View this message in context: http://tapestry.1045711.n5.nabble.com/hmac-sample-tp5716873p5716879.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
