I've been reading into Model-View-Controller and was wondering where something like a
XyzClient class would fit into this design. Splitting up MVC is easy when all you have are some views to display, some code to handle user interactions and some (maybe persistence driven) database entities.
But where does something like a
PaypalClient or a
DateFormatter class fit into? When talking of model I think of some database entity like
Course but not of some helper like
PaypalClient. Is this a model or a controller? And where does something like
DateFormatter (a helper for formatting dates) fit? Or should I prevent such classes when designing MVC (without them I would get massive controller code)?