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

Websocket example #22

Open
mips171 opened this issue Jan 1, 2023 · 4 comments
Open

Websocket example #22

mips171 opened this issue Jan 1, 2023 · 4 comments

Comments

@mips171
Copy link
Contributor

mips171 commented Jan 1, 2023

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.

@gedw99
Copy link
Contributor

gedw99 commented Jan 1, 2023

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

@gedw99
Copy link
Contributor

gedw99 commented Jan 1, 2023

But I don’t know it’s done now. It’s SSE based ?

@mikestefanello
Copy link
Owner

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.

@mips171
Copy link
Contributor Author

mips171 commented Jan 3, 2023

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

	wsocket := wsocket{Controller: ctr}
	g.GET("/wsocket", wsocket.Get, middleware.RequireAuthentication()).Name = "wsocket"
	g.GET("/terminal", wsocket.Terminal).Name = "terminal"

websocket.go

package routes

import (
	"fmt"

	"github.com/mikestefanello/pagoda/pkg/controller"

	"github.com/labstack/echo/v4"
	"golang.org/x/net/websocket"
)

type (
	wsocket struct {
		controller.Controller
	}
)

func (c *wsocket) Get(ctx echo.Context) error {
	page := controller.NewPage(ctx)
	page.Layout = "main"
	page.Name = "wsocket"
	page.Title = "Websocket Shell"

	return c.RenderPage(ctx, page)
}

func (c *wsocket) Terminal(ctx echo.Context) error {
	websocket.Handler(func(ws *websocket.Conn) {
		defer ws.Close()
		for {
			// Write
			err := websocket.Message.Send(ws, "Hello, Client!")
			if err != nil {
				ctx.Logger().Error(err)
			}

			// Read
			msg := ""
			err = websocket.Message.Receive(ws, &msg)
			if err != nil {
				ctx.Logger().Error(err)
			}
			fmt.Printf("%s\n", msg)
		}
	}).ServeHTTP(ctx.Response(), ctx.Request())
	return nil
}

websocket.gohtml

{{define "content"}}
  <div hx-ext="ws" ws-connect="/wsocket/terminal">
    <div hx-boost="true" id="chat_room" hx-swap-oob="morphdom">
      hello
    </div>
    {{template "form" .}}

  </div>
{{end}}

{{define "form"}}
  <form id="form" ws-send >
    <input name="chat_message">
  </form>
{{end}}

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

No branches or pull requests

3 participants