Websocket Squid endpoint mandatory for cursor vs offset scrolling in data?

[vit]

I see in the graphql schema that only the StreamXXX objects get a cursor to navigate in data lists.

Those objects are only available in subscription, so using a long lasting connection to the server.

As I see no websocket endpoints exposed publicly in the official list, I wander if we should be exposing and publish them to allow the use of StreamXXX objects.

A Subcription on websocket allow to make query and mutation as in http.

But http endpoints can not do cursor navigation nor subscription…

(appollo javascript client can do this, using http multipart protocol))

What is the best practice to handle navigation in graphql for the history of transactions ? What Cesium2 and Gecko are using ?

[HugoTrentesaux]

@vit

As I see no websocket endpoints exposed publicly

Some endpoints are available in websocket though. Look at duniter panel for examples (repo Hugo Trentesaux / duniter-vue · GitLab). I am using websocket to display latest indexed block in live.

This is the reason of the “upgrade” lines in squid nginx config : Duniter | Duniter squid.