Request for adding page index in to traverseiterator RpcClient method.

[RawichK]

Summary or problem description
TraverseIterator method of RpcClient has a limitation when the frontend needs data in the middle or end of the Iterator.
Therefore, developers will need to traverse the very long list of an Iterator e.g. 1,000 or even 10,000 to get the information they want in case the session was cut.

Do you have any solution you want to propose?
I proposed to add pageIndex as an additional to sessionId, id, and count. To access data from where it left of.

Where in the software does this update applies to?

• Plugins: RpcServer

[roman-khimov]

in case the session was cut.

In this case you'll need to get a new iterator and you'll really get a new one, meaning the state it has can differ from the state of the previous one (unless you're using historic invocations implemented in NeoGo). This makes paging harmful, you can easily get duplicates or miss some elements.