I agree that there isn't much time spent in the view engine but every ms counts on a enterprise site. when you have complex logic that must occur and the choice for a view engine is interpreted and takes an extra 10 ms that could be used else where for more complex logic it is well worth it to consider this. I have spent too much time on past projects trying to find ways to enhance performance to find that the big stumbling block was the backend dll's i had no control over. While MR provides so much more control over what is rendered and the wonderful end to Viewstate. I still want to make sure at this point in my project I am picking the best performing tools for the job. with a balance on the tells and technologies I wish to link up with and utilize. and the castle project provides that but the View engine is a plugable piece that I really want to make sure isn't going to be a plug in the flow.
I will do something then If any one is interested I will share my results I will put together a series of simple views reading lists of data from a single db on a single server and do some benchmark of my own. if interested I will post my results with the tested views used. I may ask for some help once I get the NVelocity views complete. to make sure I am utilizing the other engine syntax correctly. I will even create a asp.net webforms to compete it against. if there is enough interest. Please let me know if there is interest in this type of performance data. Thanks, Terry Massey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
