I'm starting to think that this flat representation of resources in
the rails-style breed of MVC frameworks is quite deficient for today's
requirements of apps. A domain is hardly flat, and the deeper you get
the more context you need
For example
/Account/1002/Subscribers/1/Lines/425-555-1010/
With today's framework's you'll end up activating the Lines
controller, passing an id. What Account/Subscribers and their ids? One
trick is to pre-load those by using hierarchical routes. MR3 routing
supports this. The issue I have is that this is too decoupled from the
controllers (they continue to be flat)
Using Routing
For("/Account/:id").Config(c => {
c.For("/Subscribers/:id").Config( c2 => {
c2.For("/Lines/:id") ...
});
});
We could potentially pre-load each account, subscriber and pass it
along to the LinesController, but I'm not convinced this is a good
design.
Thoughts?
--
Cheers,
hammett
http://hammett.castleproject.org/
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" 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-devel?hl=en.
