<snip> > Static variables in Actions are a Bad > Thing, that's a ell-known fact, but why is a Log instance an exception to > this rule? > > Is it only a bad thing to have static members that might be updated? Is > that the difference here? </snip>
The documentation for Action says: "Instance and static variables MUST NOT be used to store information related to the state of a particular request. They MAY be used to share global resources across requests for the same action." In other words, you just have to think about what you are doing, Frank. There is nothing inherently wrong with static variables. If you are storing state for a particular action in a static variable, this will clearly cause a problem. If you are storing state in a particular action where that state has nothing to do with the particular Action, that is different. Here there is no problem with using the same Log class object for distinct uses of the same Action class object. Jack -- "You can lead a horse to water but you cannot make it float on its back." "Heaven has changed. The Sky now goes all the way to our feet. ~Dakota Jack~ "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
