I am sure that the ``DataManager`` interface is not the right place for this. By design, it does not know about the view machinery.
That said, I know that there is sometimes a need for model and business logic code to know about the request. For those cases you always have the participations hooks, which any complex app uses anyways.
I am sure that the ``DataManager`` interface is not the right place for this. By design, it does not know about the view machinery.
That said, I know that there is sometimes a need for model and business logic code to know about the request. For those cases you always have the participations hooks, which any complex app uses anyways.