Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Implementation of native websockets #2

Open
ralyodio opened this issue Dec 10, 2016 · 17 comments
Open

Implementation of native websockets #2

ralyodio opened this issue Dec 10, 2016 · 17 comments

Comments

@ralyodio
Copy link

Is it possible to use native websockets instead of socket.io?

@icebob
Copy link
Owner

icebob commented Dec 12, 2016

Sorry, but not. It's only working with socket.io

@gholol
Copy link

gholol commented Dec 20, 2016

The package name is kinda misleading then as native websocket is kinda different from socketio

@sam3d
Copy link
Collaborator

sam3d commented Feb 20, 2017

I second this, it should be called vue-socketio or similar. People looking to use (or even make) a vue-websocket plugin that utilises the native websocket would be disappointed. Either way I don't believe vue-websocket is a good name for this package.

@boneq
Copy link

boneq commented Apr 27, 2017

How to use this websocket? There is no specific use

@kvnxiao
Copy link

kvnxiao commented Sep 18, 2017

Please rename this github repo to vue-socketio as this is very misleading. I was looking for a native browser JS websocket integration with vue, not socket.io.

@flip111
Copy link

flip111 commented Dec 20, 2017

I also wasted time with this library when i was looking for native websockets. By the way there is also https://github.com/MetinSeylan/Vue-Socket.io and https://github.com/nathantsoi/vue-native-websocket

@boneq
Copy link

boneq commented Dec 21, 2017 via email

@icebob icebob closed this as completed Dec 21, 2017
Repository owner locked and limited conversation to collaborators Dec 21, 2017
@sam3d
Copy link
Collaborator

sam3d commented Aug 29, 2018

I'm unlocking this issue so I can gather feedback.

It seems as though vue-websocket will be this package name, and the owner isn't interested in changing it. So, end of discussion on that particular point I'm afraid.

However, I would like to introduce and supplement the socket.io implementation with a native websockets implementation.

I wanted to see what public opinion was on this change, and whether or not it would be outside the scope of this project. I don't want to remove or break any functionality for those who do use this package for socket.io. Looking forward to hearing your thoughts!

@sam3d sam3d reopened this Aug 29, 2018
Repository owner unlocked this conversation Aug 29, 2018
@sam3d sam3d changed the title possible to use native websockets? Implementation of native websockets Aug 29, 2018
@sam3d sam3d added discussion and removed question labels Aug 29, 2018
@ralyodio
Copy link
Author

I would be interested in native sockets instead of socket.io You could always fork it and make the change. vue-websocket-native

@Nolaan
Copy link

Nolaan commented Sep 4, 2018

The example doesn't even work 😞

@ralyodio
Copy link
Author

ralyodio commented Sep 5, 2018

nope. that's why i gave up on this. if someone wants to fork it and make it native ws i'll test it out.

@sam3d
Copy link
Collaborator

sam3d commented Sep 5, 2018

Apologies while I get up to speed, I've just taken over as the lead maintainer for a while.

I'll test out the example at some point in the next few days and update it

@Nolaan
Copy link

Nolaan commented Sep 5, 2018

Thanks for the head up @sam3d it's not your fault. I'm getting very frustrated, I've started using VueJs for a personnal project 2 weeks ago and so far it looks like only roadblocks ahead.
None of the tutorial I've followed worked for any project, or seldom. I've used modules where the start function isn't starting anything and most of the time when you link up in GH the usual answer is : provide a demo project if you want us to trust you that's an issue.

I'm not sure if I will ever recommend the VueJS ecosystem.... Or am I alone in the universe?

@kvnxiao
Copy link

kvnxiao commented Sep 5, 2018

@Nolaan you are probably alone in that universe. the VueJS ecosystem is perfectly fine, functional, and growing. If you're looking for a native websocket implementation, I suggest you to try going with simply just the websocket api documentation from https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API ; that's what I ended up doing.

@Nolaan
Copy link

Nolaan commented Sep 5, 2018

perfectly fine is a little bit meh especially when I think about backward compatibility and dependencies... But probably you're right, don't get me wrong I can communicate with my server over the dev console of Chrome/Firefox (using SSL) just the module won't connect.

@sam3d
Copy link
Collaborator

sam3d commented Sep 5, 2018

@Nolaan Thank you for saying that 🙂 I'm a huge fan of the Vue.js ecosystem - it's definitely still got its fair share of teething problems that's for sure, but on the whole it's actually growing up really well.

I'm sorry to hear you're getting frustrated getting into Vue, I totally get it. I updated the README not too long ago with other alternatives to using this package for native websockets, let me know if there's anything I can do!

@ais-one
Copy link

ais-one commented Sep 11, 2018

Vue eco-system may not be as extensive or mature as React, but between the two, it is easier for me to dive in to Vue to fix things, rather than wait for someone to implement the feature...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants