> From: Bill Moseley [mailto:[EMAIL PROTECTED]] > Sent: 06 June 2002 19:06 > To: [EMAIL PROTECTED]
> My MVC efforts often fall apart in the C an M separation. > My M parts end up knowing too much about each other -- typically > because of error conditions e.g. data that's passed to an M that > does not validate. And I don't want to validate too much data > in the C as the C ends up doing M's work. This sounds like an interesting area to explore - I would quite like to get down to some specifics, for example to work through some concrete examples and bounce some designs around. Can we take a real instance where you have a problem, and see if we can develop an understanding? Will you be willing to post some descriptions of [possibly simplified] cases where you want to review your current MVC split? Or should we take a simple example and see what happens? For example, we could model a basic internet banking site - the data strunctures, range of events, presentation etc are simple and generally well understood. We can take the discussion off-line if the list feels it will be too OT. Regards Jeff
