REST Service - Server Side Paging and Session Time Out

johntalbott

Support (or anyone),

I have a static HTML panel set up for a Kendo grid. It retrieves data via an AwareIM REST Service returning JSON.

It appears that the only option is to retrieve all the records in a batch, so:
a. It takes a long time to load
b. No server-side paging is available

Is that correct? If so, is there any way around it?

When I click on another tab, I always get a "Session has timed out" Error.

Any idea what might be causing that?

Video demo: http://screencast-o-matic.com/watch/cbe2VN6z0F

CalD

Hey John, I have done a fair bit with REST over the years, limited with Aware though. Thought I'd share my thoughts...

In regards to your question 1 - server side paging, to my mind you wouldn't want this. The REST requests should be made and executed and ended server-side, no context no anything kept. Imagine you have a big system with perhaps 10s of thousands (or more) of people/systems utilising your api no way do you want your server being dragged down maintaining contexts for all those connections. Also think about you don't know exactly how client systems will be accessing your API - you need to control what you can control or all sorts of problems can occur.

So, the only option is to maintain paging within the API. Perhaps let the user specify how many records per page - or you define it. Then define the URL/parameters to contain something to identify to your server what page they are asking for.

johntalbott

CalD wrote
Hey John, I have done a fair bit with REST over the years, limited with Aware though. Thought I'd share my thoughts...

In regards to your question 1 - server side paging, to my mind you wouldn't want this. The REST requests should be made and executed and ended server-side, no context no anything kept. Imagine you have a big system with perhaps 10s of thousands (or more) of people/systems utilising your api no way do you want your server being dragged down maintaining contexts for all those connections. Also think about you don't know exactly how client systems will be accessing your API - you need to control what you can control or all sorts of problems can occur.

So, the only option is to maintain paging within the API. Perhaps let the user specify how many records per page - or you define it. Then define the URL/parameters to contain something to identify to your server what page they are asking for.

I believe we are talking about the same thing. The Kendo Server-Side operations work as you described. Paging parameters are sent in the URL, so the server-side knows what to do. The default AwareIM API knows how to handle the paging parameters.

In an attempt to decouple the UI from the AwareIM parsers, I am calling a REST service exposed by AwareIM that returns JSON directly from a manually configured grid. The paging parameters are being passed, but it appears that AwareIM REST implementation ignores those parameters and ALL records are returned to the client in a single call.