1. Flex 2 is coming. If you have a service layer you can expose it via ColdSpring's flash remoting support and call it from Flex or Flash apps with out having to change your applications architecture.
2. Reactor and other persistence frameworks are becoming more powerful. If you abstract your persistence layer (DAOs and gateways) from your Mach II listeners (or MG Controllers) then you can switch to Reactor without having to redo your listeners.
In short I believe the service layer is key in large applications when you want to reuse code and give yourself extra flexibility.
--Kurt
On 3/14/06,
Troy Simpson <[EMAIL PROTECTED]> wrote:
On Another note. I noticed that the Coldspring examples create a
mach-ii Listener Object which contains a Service Object. The Service
Object contains a DataAccessObject and GatewayObject. What is the
benefit of creating the extra Service Object layer? Why would you not
create the DataAccessObject and GatewayObject within the mach-ii
Listener Object?
I sincerely appreciate any comments. I am just a young grasshopper
among great masters of the art. ;-)
Troy
