PageFlow for large applications - Best Practices Question

Topics: Web Client Software Factory, UIP Application Block discussion, User Forum
May 27, 2008 at 4:08 PM
Hi all,

We're in the final stages of development of a large application using WCSF (~15 modules, 200 pages, custom controls, etc...) and have hit a snag in the way we developed our pageflow.  Essentially, due to the method we used (which incorporates a large number of distinct pageflows) we have ended up with a trade-off between the back button working properly and the user being redirected to the appropriate page when they re-engage with an existing pageflow that has been passivated. 

What are the best practices with pageflows in larger applications?  Should we have one pageflow for the entire application?  If we do this, will the back button work consistently?  With a large pageflow of this type, is there an effective method of segmentation for manageability or do we need to essentially keep it all in one file?  If we have a pageflow that runs into the hundreds of pages, will we have noticeable performance issues and is there a way to optimize for this? 

Any feedback on this would be greatly appreciated.