[ https://issues.jboss.org/browse/TEIID-1854?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1854: ------------------------------------- Implemented the $skiptoken functionality based on resultset caching; What I have seen other implementations do is they never have session affinity to keep track of single result set based on logged in user. Teiid implementation also does not force the user to keep the session tracking, but if the same user (based on http basic, can also easily be user name token) logged in with skip token, since original results are stored using user scoped cache, it will fetch next batch from it. If the results are expired then it will fetch from source again and reposition the cursor. If the results are expired and source is queried again there is no guarantee that same set of results are returned. If there is no ordering specified on the query the key based ordering is used on the results so that absolute positions can be used on the result sets. Also odata transport is added with defined security-domain to be used by the odata calls. remaining todo is ALL functionality before I can close this out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira