Hi Tim, Thanks for your respones. That makes me feel much more confident.
Thanks Gautam Tim Kelly wrote: > > I have used this approach in my application and found velocity macros to > be > handy for field level html elements. Then use specific velocity files to > define pages. I don't think you'll run into any memory or CPU issues with > the approach we run our production servers with 4GB of memory and dual > 2GHz > 64 bit processors. The CPU usage has never gotten above 10% with 40,000 > page views/day. I sized the JVM to run with 2GB and haven't hit any out > of > memory errors. > > Tim > > On Tue, Mar 18, 2008 at 2:59 PM, Gautam Joshi (jgautam) > <[EMAIL PROTECTED]> > wrote: > >> Hi, >> >> I am planning to use Velocity for a metadata driven UI framework. >> A velocity template at will be fed the UI metadata from the database. >> Based on this metadata, >> this template will then invoke other velocity templates. I plan to have >> templates defined for Text fields, Select Boxes, etc. >> Based on the type and number of fields defined in the metadata, the >> topmost velocity template in turn will call these other templates that >> handle specific field types. >> I do not expect the metadata to have more than 50 fields. >> Do you think this approach will cause any memory or performance issues? >> >> I would really appreciate if someone could share their thoughts and >> prior experiences. >> >> Thanks >> -Gautam >> > > > > -- > Tim Kelly > Director of Development > 275 Wyman Street > Waltham, MA 02451 > > Phone: 781.290.5300 > Mobile: 508.561.0985 > Fax:781.290.5305 > http://www.buildingengines.com/ > > -- View this message in context: http://www.nabble.com/Velocity-Question-tp16129154p16209189.html Sent from the Velocity - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
