hmm looks like you can maintain a server side recordset in the middle tier but passing on the changes to the client in this case the consumer of the web service seems to be the challenge.

I am creating a client to consume the web service so I have complete control over the client, unlike a browser consuming the service, so I should be able to make a closer coupling between the client and the webserver.

Thinking about it, it may be possible to somehow get the client to subscribe for the information, then keep track of the ip address and the page (data) the client is currently viewing and to pass updates back to the client. When the app is closed, it automatically unsubscribes from the server, and if the client falls over, then a page can only be subscribed to for 24hrs max.

I wonder if this will be possible to implement?