CODEWITHSUNDEEP
phpsessiondependency-injectiondoctrine
Jose Armesto
Jose Armesto

Reputation: 13759

Saving and initializating session values in the model

Imagine that I want to login a user. The user sends the validation data, and my controller gets the POST request so it calls a User Repository method in order to registered him.

I'd like to start the user Session with the user data. But how should I start the session? Should it start in the controller or the model? I think it should be the model, since it's my business logic who says that session have to be started. But how? Should I pass the session object to my Repository?

Im using Doctrine for the model layer, and my own framework for the rest. I use dependency injection but I don't see how to get access to the Session from the entities / repositories layer.

The only solution I've got right now is to call the repository method passing the session as a parameter, but it doesn't feel right.

Upvotes: 0

Views: 62

Answers (1)

ZolaKt
ZolaKt

Reputation: 4719

I think session handling should be done in the controller, but just personal opinion. If you are trying to have a clean separation of concern, it should defiantly be done it the controller. It doesn't make a lot of sense to make Doctrine (which has a very strong focus on abstraction and independence) dependable on the session.

Make a controller which calls a method from model to register the user. The model method returns the user specific data, which you pass to the Session (from controller). You will probably use session in a lot of places, not relevant to model. Why make it stretch to two levels, if you can encapsulate it in one?

Upvotes: 1

Related Questions