For years now I\'ve been reimplementing the same code over and over (with evolution) without finding some method of cleanly, and efficiently, abstracting it out.
I work on a project with a legacy service layer that returns null in many places if a requested record does not exist, or cannot be accessed due to the caller not being authorized. I am talking about
I\'m wondering if my service which is a layer between my ArticleRepository (Doctrine 2) and my Controller (Zend Framework) should take care of authentification/authorization or it should be part of an
quick one. What is the difference between a service and a service layer? I could not 开发者_如何学编程find a good answer on internetIn Enterprise Application Architecture, a service layer is (quite li
Currently I have a child entity that has a @ManyToOne association to it\'s parent entity. Previous developers have set this field as lazy=\"false\" to get the parent whenever needed when the session i
I\'m using Zend Framework in a project, and I\'m creating a controller only for authentication. In this project we\'ll accept that a user signs up through a account of other sites like facebook, twitt
I have a solution that uses webforms for front end & mvc for admin console. Both UIs consume a service layer via Ninject, and i am having trouble working out a subtle but rather important issue.
I\'m currently working on a project with Zend Framework & Doctrine 2, I\'m really happy with both of those tools, but I\'m wondering on how work with this special User object, which shares databas
I\'m using a Service layer, then, I\'ve alot of Service like: UserService ArticleService CommentService AuthorizationService
in my Zend Framework project, I use a Service Layer, however I don\'t really know where to handle errors.