On Thursday 11 April 2002 10:18 am, Torsten Curdt wrote: > > For an example, I have my FormValidatorAction which is Poolable, but if > > that succeeds either a FormAdditionAction or FormUpdatingAction runs, > > which either adds or updates data. Since these are fairly simple they are > > all implemented as ThreadSafe. > > Peter, could you elaborate a bit more... I haven't seen any need for a > poolable action yet. Just curious...
The action doesn't *have* to be poolable, but it makes the code cleaner as I don't have to pass as many variables around as method parameters. My FormValidatorAction validates all request params into valid and invalid buckets, rather than passing those buckets as method params I they are just class-level variables that the methods can access as needed. It used to be ThreadSafe before actions could be Poolable, but when I was refactoring it, it was much cleaner to make it Poolable. -pete -- peter royal -> [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
