Looking forward for RethinkDB connectors as a base for E2E performant responsible stack.

But when thinking about it — this subscription layer just notify client about something new, it is not transferring the data/diff itself.

That means that with correct RethinkDB subscription it would need to be piped as littlel more advanced setup — the statefull changefeed should be on graphql server side and when it will receive update, it would have that new data on server. And as a reaction (side-effect) it should also notify subscription service which deliver message to client that it needs to refetch.

Am I right?