[CFCDev] Service layer hierarchy

[Patrick Lebon]

I've been starting to use service layers in my applications (mostly with mach-ii) and I like how it gives me more flexibility as it hides a lot of the complexity (DAO, Gateways etc) from the controller but I have a couple questions regarding the best way to handle services within other services.

I am building a simple image gallery app which consists of two main services, one is the imageService which handles individual gallery items (thumb and larger image) and then I have the galleryService that manages the actual galleries (creating, naming, sorting items etc). Now, should I be using my controller to manage each of these two services seperately (which is what I currently do with my mach-ii listeners) or should my gallery service contain an instance of the image service and therefore all access to the image service be provided through the gallery service? I am starting the think that the latter is the way to go but it seems like I have some redundancy in methods if I call a function called deleteGalleryItem() from galleryService which just calls the deleteItem() function from within imageService, where I could have just directly called deleteItem() from imageService if I handle them separately.

Cheers

----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).

An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org