Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

Client example #14

Open
Grimeton opened this issue Aug 6, 2019 · 6 comments
Open

Client example #14

Grimeton opened this issue Aug 6, 2019 · 6 comments

Comments

@Grimeton
Copy link

Grimeton commented Aug 6, 2019

Hi,

I'm missing an example that shows how to use the SockJS implementation as a client to send Json RPC2 information via the connection.

KR,

G.

@vti
Copy link
Owner

vti commented Aug 13, 2019

There is no Perl client code for SockJS, the client code is in JavaScript located here https://github.com/sockjs/sockjs-client

@Grimeton
Copy link
Author

See the problem?

@vti
Copy link
Owner

vti commented Aug 14, 2019

What problem? I don't see any problem here :)

@Grimeton
Copy link
Author

Of course not. Because you always implement the protocol and write the server side application without having a client at hand for the same programming language.

Looks like the low standards in javascript are finding their way into the Perl landscape.

Really sad.

Anyway, glad we talked about it.

@vti
Copy link
Owner

vti commented Aug 14, 2019

Why do you need a Perl client in the first place? You can always use raw websockets with a SockJS server. It doesn't make any sense to use SockJS client in a non-browser environment.

Feel free to write quality Perl software and submit to the GitHub btw.

@Grimeton
Copy link
Author

Grimeton commented Aug 14, 2019

It's a pretty simple thing: You try to connect to a server that uses a specific protocol so you use that protocol on your client side, too. Works surprisingly well for decades now, no matter if it's IP, TCP, HTTP, pick your poison...

So having a SockJS server, the logical step is to get the client application and use it.

But the way I understand it, after looking into the SockJS thing is that it tries to solve a problem nobody ever had in the first place anyway. Like using all the existing methods, putting itself on top of it, creating a little bit of protocol logic and then acting as another object...

Anyway, glad we talked about it.

Cu

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

No branches or pull requests

2 participants