This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: newbie help needed!
--NzB8fVQJ5HfG6fxh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Cocoon used to publish Docbook in HTML on the fly is MUCH slower than
serving up Docbook batch converted to HTML with Apache. On-the-fly
generated or "fried" web pages have their uses. Batch generated or "baked"
web pages also have a place. A good description of the different uses
can be found here:
http://www.salon.com/contact/staff/idk/print.html
- Ryan
On Tue, Dec 24, 2002 at 09:42:16PM +0800, damar thapa wrote:
> Hi,
>=20
> Thanks for your pointer.
>=20
> The content basically is static, so your approach is perfectly fine with=
=20
> me.
>=20
> Since I found creating XML docbook documents easy, using XMLmind XML=20
> editor, I am writing in it. What I want now is a framework to publish,=
=20
> where I can concentrate on presentation and site organisation later as I=
=20
> learn xslt.
>=20
> How slow is cocoon in comparison with the option you suggested? Is it=20
> significant?
>=20
> Thanks once again.
>=20
> Damar
>=20
>=20
>=20
>=20
> Bob Stayton wrote:
>=20
> >On Sat, Dec 21, 2002 at 12:05:59PM +0800, damar@netvigator.com wrote:
> >=20
> >
> >>Hi,
> >>
> >>I am new to this list and new to both XML and docbook.
> >>
> >>Recently, I installed Apache+tomcat+cocoon and managed to published a
> >>docbook article, using docbook dtd and xsl. It is a very simple
> >>publication - docbook xsl installed, docbook article created, and made =
it
> >>point to the xsl. With my very limited XML and XSL knowledge,I could not
> >>follow the XSL files for modifications. I at least have the platform for
> >>creating documents for the future site (if I cannot call it a site now!=
).=20
> >>
> >>Now, I read about docbook's website framework for publishing webpages.
> >>Again with my limited knowledge, I have no clue how I should start this
> >>with -- could not follow the instruction given in the example
> >>webpage.
> >>
> >>Can any one give me some hints on the basics of docbook and website
> >>framework? How can I publish example site on cocoon? It may give me some
> >>hints afterwards.
> >> =20
> >>
> >
> >You haven't described your application much, so it isn't
> >clear to me why you want to combine DocBook and Cocoon.
> >
> >Cocoon is generally used to convert on demand an XML
> >document to an HTML document and deliver it over the wire.
> >Doing so with DocBook XSL often leads to dissatisfaction
> >with the performance, because the DocBook XSL stylesheets
> >are big and complex, and don't usually process within the
> >response window most people expect for browsing. If your
> >XML files are fairly static, you might be better off
> >converting the XML to HTML outside of Cocoon and simply
> >serving the HTML with Apache. The response time will be
> >much better, and you won't be loading down the server
> >with a lot of intense DocBook processing.
> >
> >Website is an extension of the DocBook XSL stylesheets to
> >generate a set of web pages that make up the navigational
> >tree for a web site. You create XML input files that define
> >the web pages using the website DTD, and then process
> >them with the website stylesheet to generate HTML.
> >The result is a set of HTML files that contain the
> >web pages a user can navigate through on the site.
> >
> >I don't think you can use website with Cocoon because
> >website generates multiple HTML files from the input XML. =20
> >A server can deliver only one HTML file to a browser in
> >a single request. It could cache the rest of the files,
> >but then you might as well just generate the HTML
> >ahead of time and serve that with plain Apache.
> >
> >Hope this helps.
> >
> >
> >Bob Stayton 400 Encinal Street
> >Publications Architect Santa Cruz, CA 95060
> >Technical Publications voice: (831) 427-7796
> >The SCO Group fax: (831) 429-1887
> > email: bobs@sco.com
> >
> >
> >=20
> >
>=20
>=20
>=20
>=20
--NzB8fVQJ5HfG6fxh
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE+CSxc6ZA8+1/wXqMRAuA2AJ9Hb1J84xXLGDkJgqO7JVUFAnt+kQCfRxE2
obpN8qNMzjN2Wx5w9+ZU2yk=
=4XDs
-----END PGP SIGNATURE-----
--NzB8fVQJ5HfG6fxh--