[TYPO3-mvc] filter and pagination views of own extension really slow

[Daniel Hirth]

> I don't get why you have the if-count as it is the same partial as in the
> paginate widget?!

Because our client does not want the paginate widget to show an unresponsive single "1" if all result items fit to the first page. Instead the page number should be hidden. As far as i know, the paginate widget does not have the option to hide the page numbers if only one page is needed, so I tried to solve this with some nested conditions. But i would gladly remove them if it would be otherwise possible to solve this. 

> Your problem with the filter object is the casting to an argument array. I'm
> not sure but usually objects are referenced by their id. But as you are
> using an object which isn't stored in the database and has no identity it
> cannot be reference at all.

> Why don't you use an array?

To me, it made sense to stick with the given formats of objects and properties, even for form filters, so you can use the same functions to work with those filter properties, especially storage objects, as when working with model objects. But I do not insist on this, so i converted the filter object to a filter array, which now seems to work fine between the cached and non-cached actions. 

I think those tips did a great job of improving the overall performance of the extension, thanks again for that.