XPages: Which is better: more pages or more dynamically rendered controls?

I am building an application using XPages that involves showing six different kinds of users six different views of information from a Notes document and each of those views has an edit mode and a read mode.

Does anybody know if better server performance is normally achieved through “more pages/less dynamically rendered custom controls” OR “less pages with more dynamically rendered custom controls”?

=====Additional details =======

My approach is to build a single page for editing and a single xpage for reading and then render the appropriate custom controls per user role.

A different approach might be to have a single xpage per role and have each of those pages contain both edit mode and a read mode custom controls.

Subject: I think less is better…

Less XPages and more dynamically rendered controls is better. Better for maintenance and the hit on performance shouldn’t be that noticeable - if it is then this ought to be corrected.

Have you any performance results to hand that might deter you from going down the dynamic controls route?

Subject: I was hoping you would say that…

Thanks for your response, Paul.

No results yet because I am really just getting into the meat of the application now but it seemed to me like making the server manage things more at the component level was preferable although trying to develop everything into a single page seemed to be cumbersome from the developers perspective. I forgot to mention that the application is in English and Portuguese.

I am going to proceed with the two page/dynamic components approach and update back here.

Subject: Let us know how you get on…

… and email me if you have further queries...paul_hannan@ie.ibm.com