-
Notifications
You must be signed in to change notification settings - Fork 118
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
Websocket example #22
Comments
I use NATS.Go to do all that. nats.Go can work in a web client when compiled to wasm. For non web clients it just works of course. I have done it this way with go-app projects as well as GIO projects. Using nats gives you security, kv, workers and other stuff. It also means you can stop using REST or GRPC because it does all that too. for pagoda you can easily do hook up htmx stuff to use it from the server. In the web client it’s very easy to use. When you get sent something from the server ( will be html in this case ) you can just call Js from the golang wasm to update the DOM. It’s pretty cool way to do things I have found. hope I have explained myself reasonably |
But I don’t know it’s done now. It’s SSE based ? |
I'm glad to include an example if someone wants to work on it. It's not something I have time to do right now, but if that changes, I'll consider putting something together. |
I was going to contribute an example but was unable to invoke the websocket handler function from the echo route group. I must be doing something wrong there. Not sure, but I think it's re-rendering the outer page, since it's set to render that page on GET of the outer route before it reaches the websocket route? router.go
websocket.go
websocket.gohtml
|
Any chance of including a websocket example using HTMX? I haven't been able to get the official docs example to work, but I'm probably overlooking something. Anyway, would be nice to establish a pattern for it here.
The text was updated successfully, but these errors were encountered: