Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 50026 invoked by uid 500); 7 Jan 2002 19:39:31 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 50015 invoked from network); 7 Jan 2002 19:39:30 -0000 Subject: Re: What are content management and middleware? From: Rick To: cocoon-users@xml.apache.org In-Reply-To: <000501c196fd$75c631e0$c9d0403e@stephenmclarke> References: <000501c196fd$75c631e0$c9d0403e@stephenmclarke> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: 07 Jan 2002 13:39:33 -0600 Message-Id: <1010432374.14319.17.camel@punkadoodle.soils.wisc.edu> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N content management, as used in this industry, usually encompasses user-access tools as well as organization and presentation. for instance, grabbing a bit of marketing jargon at random, "Insite Server, a 100% browser-based, out-of-the-box content management software that allows teams to create, edit, manage, revise and publish Web sites and intranets." middleware is software that allows applications to talk to each other. CORBA is middleware; RMI is middleware; Java Message System is middleware. the customary use of the term refers to *products* that implement middleware, along with various value-added services. SonicMQ is a middleware package. cocoon is really none of the above. cocoon's content architecture (separating logic from styling from content from management) simplifies content management, but doesn't do it for you. for example, if i want to give access to FNORD.XML to our "content" people, FNORD2HTML.XSL to our "design" people, and keep all the administrative powers to myself, i have to work out all the ins and outs of file permissions, user accounts, and suchlike. without cocoon, it'd be even worse. hope this helps, rw On Sun, 2002-01-06 at 15:59, Stephen Clarke wrote: > Hi, > > This may be too basic a question. Can someone explain to me the > difference between content management, middleware, and cocoon. I > thought content management was just building an XML/XSLT system > for separating content from design. But now it seems that it's > more like cocoon facilitates building middleware and that > XML/XSLT is just a tool of the job. What exactly is meant by > these terms, content management and middleware. > > TIA. > ---- > regards, > > Stephen Clarke > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: