Option to silently ignore invalid requests about sharedb HOT 7 CLOSED

Custom message passing can be implemented on top of the message 'receive' client event / middleware hook:

Server:

backend.use('receive', function(request, next) {
  var data = request.data;
  if (data.myApp) {
    // Handle app specific messages and don't call next
    return;
  }
  // Call next to pass other messages to ShareDB
  next();
});

Client:

connection.on('receive', function(request) {
  var data = request.data;
  if (data.myApp) {
    request.data = null;
    // Handle app specific message
  }
});

Send a message from client:

connection.send({
  myApp: 'messageType',
  ...
});

Send a message from server:

agent.send({
  myApp: 'messageType',
  ...
});

The agent is available in all middleware, so on the server you could send a message in reply to a message from the client, or send a message to the client from the 'connect' middleware as soon as the client connects, for example.

Let me know if that solves your issue!

from sharedb.

Is there any way to send a message from the server to all connected clients? I think agent.send will send reply to only 1 client. Am I correct?

from sharedb.

@RisingGeek this doesn't sound related to this issue? What's your use case here?

from sharedb.

I am trying to make a real-time editor using sharedb and want to add video calling feature. Using socket io gives errors and when trying to use middleware provided by sharedb, server sends reply to only 1 client because it's ignoring it. I want a listener on client side for custom events.

from sharedb.

I'm not sure I understand what video calling has to do with ShareDB? Do you mean you're trying to send custom messages down the same socket ShareDB is using? In theory it's possible, although probably not advised. Can't you just open up a separate websocket, and send messages using whatever websocket protocol you want?

from sharedb.

Yes, I was sending custom message in the same socket that sharedb is using. Thanks for the advice. I will use a separate websocket.

from sharedb.

Custom message passing can be implemented on top of the message 'receive' client event / middleware hook:

Server:

backend.use('receive', function(request, next) {
  var data = request.data;
  if (data.myApp) {
    // Handle app specific messages and don't call next
    return;
  }
  // Call next to pass other messages to ShareDB
  next();
});

Client:

connection.on('receive', function(request) {
  var data = request.data;
  if (data.myApp) {
    request.data = null;
    // Handle app specific message
  }
});

Send a message from client:

connection.send({
  myApp: 'messageType',
  ...
});

Send a message from server:

agent.send({
  myApp: 'messageType',
  ...
});

The agent is available in all middleware, so on the server you could send a message in reply to a message from the client, or send a message to the client from the 'connect' middleware as soon as the client connects, for example.

Let me know if that solves your issue!

I have applied this for passing custom messages but it gives an error Ignoring unrecognized message { while sending message from server

from sharedb.