MVC question about life itself as a hole.

What should go where?

I have the following classes: logger, database connection, template engine, request and response in my FastCGI app software. Since sending everything to the controller and models is considered a bad practice, the same way as sending the application object itself, I decided to create a context class which holds everything related to the actual request being processed.

What should go in the context class and in the main class? Request and response are obviously in the context class, since they are request-only, but what about the rest?

Sorry to bother /prague/ with my ENTERPRISE MVC SOLUTIONS. I'm also using no framework.

get out of here faggot or i'll hack your company's gibson

>>2
Woahhh! B-but my company's not gay... or is it? Anoooonnn pls don't ;-;

>>1
I don't like MVC. Therefore I don't know anything about it. Isn't that some UI design crap?

>>4
It's a development model, or a ``designfaggot pattern''. It's shit though.

I always thought MVC was just a collection of common sense about separation like ``if you store your model in the label of a button, you're doing it wrong''.

MFC > MVC

KFC > MFC