On Jun 14, 2005, at 3:30 PM, Bertrand Delacretaz wrote:
Le 14 juin 05, � 20:35, Glen Ezkovich a �crit :
...The current use of actions as I see it is for small general-
purpose things, but not for application-level processing, which
should be orchestrated by the flow engine (be it flowscript of
javaflow)
Then the DatabaseSelectAction shouldn't be used as an example to
access Employee data from the database but the HTTPHeaderAction
would be a good example of how one can set the response headers?
I'd say yes, but it's not a black and white thing.
Never is. What I'm looking for is just a baseline for novice users.
As they gain experience and sophistication, I would expect them to
make their own decisions based on the use case and resources
available. I don't want to provide an example that would violate
basic best practices.
Glen Ezkovich
HardBop Consulting
glen at hard-bop.com
A Proverb for Paranoids:
"If they can get you asking the wrong questions, they don't have to
worry about answers."
- Thomas Pynchon Gravity's Rainbow
