Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add stream docs #129

Closed
wants to merge 1 commit into from
Closed

feat: add stream docs #129

wants to merge 1 commit into from

Conversation

mmeloni
Copy link
Contributor

@mmeloni mmeloni commented Aug 7, 2023

This PR add docs related to new chain stream api

func main() {
tlsConfig := tls.Config{InsecureSkipVerify: true}
creds := credentials.NewTLS(&tlsConfig)
cc, err := grpc.Dial("staging.stream.injective.network:443", grpc.WithTransportCredentials(creds))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the correct way to specify the URL? I think we should be using a network instance (with common.LoadNetwork) as in all other Go examples

Copy link
Contributor Author

@mmeloni mmeloni Aug 8, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the idiomatic go gRPC way to connect to a grpc server. In others example there is the need to use more sofisticated connection solutions in order to interact with the chain. Streamer is a simple grpc readonly server that does not requires to use such complexity. For golang developers this is very easy to read.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I got your point. When we will deploy prod stream dns I will change this part, ty

Copy link
Contributor

@aarmoa aarmoa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me since we are going to update the example when all other environment URLs are available

@aarmoa
Copy link
Contributor

aarmoa commented Nov 2, 2023

Closing this PR because its changes have been included in #139

@aarmoa aarmoa closed this Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants