Hello;
manage and deploy the html. Although very many of the html pages will
be identical (particularly the smaller components), the front page,
the layout, and a couple of other pages may vary between the sites.
Something that has worked quite well for me on one project is to do
the 'changing pages' with XML/XSLT out of WO. I have documented this
in a STEPWISE article...
http://homepage.mac.com/andrewlindesay/le/articles/wo_xslt_article.pdf
...and you can check this out here...
http://www.artfind.co.nz/
You ought to keep the 'transform' cached in the application server's
memory so that it doesn't keep parsing the XSLT file which takes a
wee bit of resource that you are best to avoid on each R-R cycle.
There are a number of ways of getting the XSLT in there with the most
straightforward being a load off a private HTTP server.
This might work for your scenario.
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
