The fiddle above is what I have currently and it does work … if you only use 1 part of the mixin at a time.

For example, if I got to page 2 but then decide to filter the content down my window.location drops the page # and throws up the filter.

Or if I start filtering, but then decide to hit page #2 the filter is dropped from window.location and the page is added.

The reason my use case requires this is for a simple “copy / paste” situation where my customers want to share a url and in doing so they really benefit from the full context (ie- what page/search/sort was used to achieve the desired view into the controllers model)

So a legit url with all the data might look like this

/records/#/page/2/sort/username/search/dave

My question here is really about the ember v2 router api -was it designed for this scenario? If not today could it be in the future? What would need to change to support this?

Also for the stackoverflow like response -is there something I’m doing above in the fiddle that is causing this not to work when it is technically possible?

@toranb why are you doing the paging on the client? I’m currently doing it on the server and just adding to the array as those pages come in… How much data are you dealing with for this? It seems like a waste to receive hundreds of rows if the user only rarely changes their sorting…

@i_am_brennan this was both a conceptual problem and a “here is one implementation” -so about the pagination client side only … not a great long term solution clearly. I’d actually really like to see what your server side pagination looks like. Are you using ember-data or is this home grown? could you throw together a jsfiddle for others like me who are looking for solid solutions to the common line of business problems (ie- pagination/sorting/filtering)