Martin Cooper wrote:
> I think it's about time we all got on the same page as regards whether these
> thingies are called modules or sub-apps. I believe we decided on modules a
> while ago, but many of us are still referring to sub-apps. The User Guide at
> this point has a mixture of both.
>
> It's going to be confusing to people if we aren't consistent ourselves, so I
> think we need to make the decision here, and then all evangelise the
> selected terminology on both lists.
>
> So, are they modules, or are they sub-apps?
>
> My personal preference is modules, but I'm capable of typing either when
> necessary. :-)
`Sub applications' for me, but I can live with `modules'. Also this is the term
that Chuck Cavaness used in his up-and-coming book. So if you dont want to
confuse all the potential new users that suddenly come along ....
( I got to go sleep now 02h34. I will have to catch up with the
discussion until Friday. Unfortunately I am away all day on Thursday.)
At the mo, I understand that there is just one level of sub applications
that can work reasonably well e.g "config/sub1", "config/sub2" and you
guys (and gals) are thinking of extending this to its natural conclusion
"config/usa/ny/ny"
"config/europe/spain/madrid"
"config/europe/spain/barcelona"
"config/europe/england/london"
then I might suggest that maybe you take a leaf from "Log4J" categories.
* define arbitary tree paths and nodes.
* define arbitary struts "category" that you can always get the root from.
Have I bitten off more than I can chew or barking up the wrong tree?
--
Peter Pilgrim
ServerSide Java Specialist
My on-line resume and for interview videos about myself, J2EE
Open Source, Struts and Expresso.
||
\\===> `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
