Hi all!

I have almost completed the web part of my framework built on ASP.NET
and other things. My intention is to port as much as possible from
tapestry while maintaining compatibility with existing components,
though I couldn't adopt the concept completely because ASP.NET's
internal code is inconsistent and quite messy.

Due to the difficulties of using view state, I choosed rewinding to
restore view before postback handling, which seems to be simple and I
expect it to be faster (with 2nd-level data cache) and more scalable.
However, I'm very new to MVC web frameworks, and I never used
rewinding before, so I would like to know from here if anyone have
experienced big problems with it? (other than mis-matched form IDs,
which could be easily avoided with a rational page design)

BTW I'm wondering if I should add initialization methods that match
the query string, like this:

/ArticleList.page?id=100&page=5

will invoke initializeView(int id, int page) // check both of
parameter names and their order


any suggestions are welcome :)

Reply via email to