I've a json rpc server with websocket transport only.
Does any one knows about a javascript library that implement json rpc over websocket that I can use?
Regards,
Related
I am using websocket with spring boot and stomp messaging protocol, where i created a HTML and using javascript event listener code to publish and subscribe the data. I can see publisher data in network tab and i can process the request in java as well. but subscriber data not showing. could any one help on this?
I have researched this topic online and have found nearly-similar questions to this - But, I need to know why in NestJS we have to use two packages to implement WebSocket communication.
The two packages are,
#nestjs/websockets
#nestjs/platform-socket.io
I understand that WebSocket is the protocol and Socket.IO is a library which has both server and client versions of it.
In the gateway file of NestJS when implementing a WebSocket connection, one has to write code similar to below.
import {
ConnectedSocket,
MessageBody,
OnGatewayConnection,
OnGatewayDisconnect,
SubscribeMessage,
WebSocketGateway,
WebSocketServer,
} from '#nestjs/websockets';
import { Server } from 'socket.io';
My questions,
What is the difference between WebSocketServer and Server here?
Why do we import Server from socket.io and not #nestjs/platform-socket.io?
How do you describe the purpose of using each of these packages in a single sentence?
#nestjs/websockets is the base package that makes websocket integration possible in NestJS. #nestjs/platform-socket.io is the specific package for socket.io integration, rather than something like #nestjs/platform-ws which is for the ws package.
WebsocketServer is the decorator to tell Nest to inject the websocket server, Server is the socket.io type for the server.
We import Socket from socket.io because #nestjs/platform-socket.io is really just for the websocket adapter that plugs into Nest's platform.
Single sentences:
#nestjs/websockets: allows for websocket communication via a websocket adapter
#nestjs/platform-socket.io: socket.io websocket adapter to allow for socket.io websocket communication with the server
socket.io: a websocket implementation and engine that is usable with and without NestJS
We already have the Twrip-RPC which provides rpc and rest endpoints . then why we need the
grpc-Gateway . What advantages it's providing compared to twirp. Is it like we can provide custom endpoints with grpc gateway is that the only difference. what grpc-gateway which Twrip-rpc can't do?
Twirp and gRPC gateway are similar. They both build API services out of a protobuf file definition.
Main differences:
gRPC only uses protobuf over HTTP2, which means browsers can't easily talk directly to gRPC-based services.
Twirp works over Protobuf and JSON, over HTTP 1.1 and HTTP2, so any client can easily communicate.
gRPC is a full framework with many features. Very powerful stuff.
Twirp is tiny and small. Only has a few basic features but it is a lot easier to manage.
To generate the RPC scaffold using the RPC framework for Go RPCs, we can consider gRPC from the beginning or look towards a more simple Twitch RPC, i.e. Twirp.
Common reasons for choosing Twirp over gRPC are as follows:
Twirp comes with HTTP 1.1 support.
Twirp supports JSON transport out of the gate.
gRPC re-implements HTTP/2 outside of net/http.
And reasons for gRPC over Twirp are:
gRPC supports streaming.
gRPC makes wire compatibility promises.
More functionality on the networking level.
Twirp supports JSON-encoded requests and responses in addition to the binary Protobuf-codec while it still behaves as an RPC. You can use HTTP POST on an endpoint like /twirp/MyService/SayHello with a JSON payload and receive a JSON response. Very similar to standard gRPC except optionally JSON.
For gRPC Gateway it's a little different. Here you can configure any HTTP REST endpoint on existing gRPC service. For example, MySevice.SayHello can map to GET /hello. This makes it very easy to implement a complete REST service on top of your gRPC definitions.
Hope this clarify it.
I have a STOMP over websocket client server implementation. I want to test my java websocket client implemented using javax websocket on eclipse jetty for different websocket errors that can come. Is there a websocket simulator that can send different websocket error codes that I wish to test ?
My websocket server is implemented using spring websockets.
http://activemq.apache.org/websockets.html says that these guys have implemented stomp over web sockets functionality. How is it different for the normal web sockets solution provided by Dojo's cometd? I thought web socket spec defines its own message structure and all? How does the HTTP upgraded web socket differs from this stomp over websockets? Would really appreciate some expert opinion guys.
Thanks,
Bhanu
The cometd implementation uses the Bayeux protocol, while the Apache implementation uses WebSockets.