RE: reusable controllers and session objects
"Schnitzer, Jeff" <[email protected]>
| Newsgroups | gmane.comp.web.maverick.general |
|---|---|
| Message-ID | <[email protected]> |
> From: Valeri Sarantchouk [mailto:[email protected]] > > But what about old good servlets? My simple tests comparing > chains of JavaBeans with analogous servlet filters shows > filters more performant. I'm not sure what you mean by this - JavaBeans vs filters? > If I can take more of your time, what do you think about > multi-action controllers? For cases of related but small > in processing weight actions, it's might be appropriate to > invoke a single (static) method instead of a class based > on the url query parameters. Is ControllerSingleton / > FormBeanUser everything we would possible want for > multi-action controllers? You certainly can do this with ControllerSingleton - but why? Is it really that hard to have lots of individual classes, one for each action? What do you hope to gain? I find that "lots of little classes" is far more convenient than "few big classes", especially with several engineers and version control. YMMV though. Jeff Schnitzer [email protected] ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ [INVALID FOOTER]