-
Notifications
You must be signed in to change notification settings - Fork 26
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
Golang wasm client for sdk v5 #68
Comments
Hello, thx! TBH I do not understand what you mean when saying about v5 API - it's mostly the same we had before with some improvements and dropping legacy. I am not sure about Go and WASM development in general, if you remember we had a prototype of centrifuge-go working in WASM - centrifugal/centrifuge-go#68 - and it's very controversal, not sure I am ready to commit to it at this point - don't see enough interest from the community. Do you suggest something different here though? |
All the problems with compilation and size will not be a problem nw. gotip compiles wasm and wasi fine now. You don’t need tinygo which is slow to compile too. so it’s probably worth revisiting that code and using the new v5 api which has no GRPC dependency, which is always a problem with wasm and browsers . i don’t have time to dig into this due to work. Web sockets and json will be way easier . |
No idea what you mean here, nothing changed in v4 -> v5 in regards to that. All changes outlined in Centrifugo v5 release post |
hey all,
@FZambia hope all is well in your new home !!
congrats on the new v5 api. It sure looks good from what I can see so far..
Do you think it’s possible with the new v5 sdk to do a golang wasm PWA style Client ?
This is where we have the web manifest and service worker code . Then it’s just golang compilation to wasm and that’s basically it I hope :)
protobufs and wasm might be a problem . Not sure as I have not yet deeply looked into the new v5 sdk.
The text was updated successfully, but these errors were encountered: