I think it would be best if we reserved the term "modules" for the future; in almost all respects, the Struts apps that are referenced by some path off the context root are really little web applications themselves, hence the term "sub apps" [I don't care if it has a hyphen or not] is more descriptive, and should be the term that's used.
In fact, until you brought it up I didn't even know that the term modules was in use. I must have missed the discussion about deciding to use "modules"; I would have put forth the comment I made in the first paragraph in favor of using "sub apps". > -----Original Message----- > From: Martin Cooper [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 16, 2002 6:03 PM > To: '[EMAIL PROTECTED]' > Subject: Terminology: modules versus sub-apps > > > 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. :-) > > -- > Martin Cooper > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
