Hello Chaps,
I've been working with both CS and MG for a while now and we're getting on
famously together, It took me a while to feel comfortable with relinquishing
that control over to the frameworks, but once done I can genuinely feel the
development benefits, it's quite amazing.
This
The fact that you're using Model-Glue should make no difference at all. If
it is, then you're thinking about it the wrong way. I see a few problems
with what you've said:
- AOP is really meant to eliminate duplication by encapsulating a
generic, common process so that it can be reused
Subject: Re: AOP in ColdSpring and ModelGlue
The fact that you're using Model-Glue should make no difference at all. If
it is, then you're thinking about it the wrong way. I see a few problems
with what you've said:
- AOP is really meant to eliminate duplication by encapsulating a
generic
access to
the event object.
Thanks again mate,
Rob
-Original Message-
From: Brian Kotek [mailto:[EMAIL PROTECTED]
Sent: 08 October 2007 15:10
To: CF-Talk
Subject: Re: AOP in ColdSpring and ModelGlue
The fact that you're using Model-Glue should make no difference at all
On 10/8/07, Robert Rawlins - Think Blue [EMAIL PROTECTED]
wrote:
Hello Brian,
Thanks a great deal for the detailed reply, it does help make things a
little clearer. You're right to say that my example was hardcoded values
and
this would most defiantly be difficult to validate using AOP,
: 08 October 2007 16:04
To: CF-Talk
Subject: Re: AOP in ColdSpring and ModelGlue
My understanding of AOP is that it really shouldn't affect the process
flow of a request. Partly because it would be messy for it to have
access to the request (event, or whatever). And partly because it just
isn't what
On 10/8/07, Robert Rawlins - Think Blue [EMAIL PROTECTED]
wrote:
Thanks Matt,
I generally agree with you that it works best when not interrupting the
application flow, i.e logging, however, It seems that everyone is quite
happy to utilize AOP to implement security concerns, and obviously
-Talk
Subject: Re: AOP in ColdSpring and ModelGlue
On 10/8/07, Robert Rawlins - Think Blue
[EMAIL PROTECTED]
wrote:
Hello Brian,
Thanks a great deal for the detailed reply, it does help make things a
little clearer. You're right to say that my example was hardcoded values
and
this would most
On 10/8/07, Robert Rawlins - Think Blue [EMAIL PROTECTED]
wrote:
Now I agree that you should really be validating every business object,
however I'm thinking about building this proxy layer between the
controller
and the model, and all data coming from the controller is generally user
2007 17:05
To: CF-Talk
Subject: Re: AOP in ColdSpring and ModelGlue
On 10/8/07, Robert Rawlins - Think Blue
[EMAIL PROTECTED]
wrote:
Now I agree that you should really be validating every business object,
however I'm thinking about building this proxy layer between the
controller
and the model
I'm working on a validation system for Transfer (but the idea would probably
port to other kinds of objects) that has a generic Validator class to handle
common needs like required fields, field length, type, etc. But you can then
define custom validation methods as well, which a subclass of
11 matches
Mail list logo
