[TYPO3-mvc] webservice instead of database as data provider
Thomas Mammitzsch
thomas at visualworx.de
Tue Oct 12 17:09:32 CEST 2010
Am 12.10.2010 16:50, schrieb Steffen Müller:
> IMO the majority of cases are read only actions. They could be solved in
> theory by:
>
> - coding a repository which fetches data from the webservice and
> instantiates the model object,
> - coding the correspondent model without setters, where the constructor
> sets the properties using the values from the repository.
>
> The model provides data with usual getters and can be used transparently
> in extbase/fluid.
>
> If pages change too often and webservice has limited performance,
> caching of fetched data could also be an option.
>
I also thought in that direction of creating an own repository.
I'm curious if i run into problems because the model will have no tca to
match against.
But maybe thats only relevant when it comes to persisting, i'm not sure.
I'll give it a try.
More information about the TYPO3-project-typo3v4mvc
mailing list