Subscribe to multiple events over a socket?

Question

1.00/5 (1 vote)

See more:

I want to be able to use a single socket if possible to subscribe to multiple events of the same type (but with different parameters) over the socket of the same type, in order to keep track of various data streams over the same socket if at all possible.

What I have tried:

I can use different sockets to connect to a host server, with each socket subscribing to one event. However, this seems like it is perhaps inelegant and/or inefficient.

Posted 1-May-22 15:47pm

LF FF

Updated 2-May-22 7:16am

Add a Solution

Comments

OriginalGriff 2-May-22 3:01am

This is not a good question - we cannot work out from that little what you are trying to do.
Remember that we can't see your screen, access your HDD, or read your mind - we only get exactly what you type to work with - we get no other context for your project.
Imagine this: you go for a drive in the country, but you have a problem with the car. You call the garage, say "it broke" and turn off your phone. How long will you be waiting before the garage arrives with the right bits and tools to fix the car given they don't know what make or model it is, who you are, what happened when it all went wrong, or even where you are?

That's what you've done here. So stop typing as little as possible and try explaining things to people who have no way to access your project!

Use the "Improve question" widget to edit your question and provide better information.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Greg Utas · Accepted Answer · 2022-05-02T07:16:00

I don't know what you mean by "events" and "parameters" in your question. But you mentioned data streams, so I assume you're using TCP, or something that runs on top of TCP.

A TCP socket usually communicates with one peer, from which it receives a single data stream. That stream can deliver a sequence of events and parameters, but you need to frame them (that is, decide where they begin and end). When you read() from the socket, you might receive multiple "messages" or only a partial message. If you're using a protocol that runs on top of TCP, it might help you decide where the events and parameters begin and end. If not, you need to buffer incoming data until you have complete events or parameters that you can pass along to your application.

It sounds like everything is arriving from the same host server. So far, so good. But if you're accessing different services simultaneously, it is quite likely that you need a separate socket for each one. To avoid that, the server would most likely have to support requests for different services over the same socket, and multiplex the messages from those services onto that socket when replying to you.

If you are sending your initial requests to the server to different well-known port numbers, you will almost certainly need to keep using separate sockets.