Hi Jeff, I am doing something similar for my projects. I use XSLT templates to generate all web views statically. I do it because I want to: (1) apply common look & feel to individual .vm, .jsp, and .html pages; (2) do it offline, to avoid any dynamic view compositions.
Disadvantage of creating web content statically is the longer development cycle. Advantage is performance. Probably it's not not the best solution for all situations but in certain cases, I think, it is. Ragards, Valeri --- --------- Original Message --------- DATE: Thu, 10 Jul 2003 11:56:18 From: "Schnitzer, Jeff" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: >I don't know, but my guess is that for any sophisticated application the >bottleneck will be elsewhere (DB calls, synchronization of shared >resources, etc). > >I've been thinking of a new approach to applying navigation bars and >titles. Rather than compose the whole page dynamically at runtime >I've been thinking of using the fact that Velocity has a very >XML-friendly syntax; it's easy to embed Velocity instructions in an XML >document. > >This would seem to make it easy to use XSL to apply all the headers and >navigation to XML/velocity pages at build-time, resulting in complete >velocity pages which need only be executed in linear fashion at runtime. >This would offer the most flexibility and the best performance, at the >cost of additional build-time complexity. > >Somebody suggested something like this a long time ago on velocity-user, >but I haven't heard of anyone actually implementing it. > >Does anyone have any experience doing this? > >Thanks, >Jeff Schnitzer >[EMAIL PROTECTED] > >> -----Original Message----- >> From: DEO Kedar [mailto:[EMAIL PROTECTED] >> Sent: Thursday, July 10, 2003 9:00 AM >> To: [EMAIL PROTECTED] >> Subject: [Mav-user] Sitemesh or view transforms? >> >> Hi, >> >> All of the pages im my application have top menu navigation, and side >> navigation bars, which are seperate pages. I want to know if there is >any >> performance metrics available of using maverick view transformation, >and >> using Sitemesh to assemble the page. If no metrics, at least any >thoughts >> on this? >> >> The menus and side navigation are role based, so there will be lot of >> logic going into building these side and top nav views. >> >> Thanks, >> Deo >> >> >> >> ------------------------------------------------------- >> This SF.Net email sponsored by: Parasoft >> Error proof Web apps, automate testing & more. >> Download & eval WebKing and get a free book. >> www.parasoft.com/bulletproofapps >> [INVALID FOOTER] > > > >------------------------------------------------------- >This SF.Net email sponsored by: Parasoft >Error proof Web apps, automate testing & more. >Download & eval WebKing and get a free book. >www.parasoft.com/bulletproofapps1 >[INVALID FOOTER] > ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 [INVALID FOOTER]
