Re: aspbeans
- From: "theath" <theath@xxxxxxxxx>
- Date: 14 Jul 2005 21:18:57 -0700
well, take a somewhat large form with a complicated datagrid. you can
populate, save, navigate through the columns by hand, and do all of
that good stuff with one line of code for each way of the transfer, or
you can do it with 2 lines of code (not counting xml situps).
that you can make changes in one layer without having to significantly
alter another, or hopefully not at all, is a fairly big benefit i
think. further, it reduces ties between the controller and the
presentation, enforcing MVC paradigms better.
that's where i see the benefit. things like RoR and JSP already offer
(fairly similar) ways to do this, but i didn't know of anything that
did it in .net so i slapped one together.
i'm planning on putting in validation, so you can write custom
validators without having to pollute your code with that either.
the main idea, i suppose is to reduce redundant code and allow
developers to focus on their logic and control, instead of doing tons
of trivial stuff. if you've got any suggestions that you'd think would
make it more clearly beneficial to you, i'm definitely open to them :)
if it's a small project, though, then it might be a pain to implement
the separate layers and everything else. i'd say the same goes for
things like (n)hibernate, ibatis, struts, or anything else.
.
- Follow-Ups:
- Re: aspbeans
- From: TJS
- Re: aspbeans
- From: Klaus H. Probst
- Re: aspbeans
- References:
- aspbeans
- From: theath
- Re: aspbeans
- From: TJS
- Re: aspbeans
- From: theath
- Re: aspbeans
- From: TJS
- aspbeans
- Prev by Date: Setting Focus on Edit Row in Datagrid - how do I reference new clientid name???
- Next by Date: Re: Faking subdomains for development computer.
- Previous by thread: Re: aspbeans
- Next by thread: Re: aspbeans
- Index(es):
Relevant Pages
|