How do I create an array of websocket connections in express js listen for matches in api query?

Question

0.00/5 (No votes)

See more:

Okay so I'm making a project that let's a user query an api using their own input.
I want to create a webhook or websocket system that when a user creates an api query a new websocket connection is made and listens for matches in the query parameters of the api query and when a match is found the webhook or socket sends a message to the server with the matching information.

Is this possible? Is so how should I go about doing it and how could I encapsulate an api query into a websocket connection. I'm just looking for a nudge in the right direction.

What I have tried:

Using AI and Google. I've managed to get some what of an idea what I have no idea where to start in embedding the api query into the websocket connection so that it listens for matches in the api's dataset.

Posted 24-Nov-23 9:51am

daniel wakeley

Add a Solution

Comments

Dave Kreskowiak 25-Nov-23 12:04pm

Your question makes no sense. The server should be providing the API clients call. As for the websockets, there server normally keeps an array of connections to clients the server can use to send out-of-band data to the clients. In this case, out-of-band refers to any data the server has to send to clients without the clients requesting it over HTTP.

daniel wakeley 17-Jan-24 12:02pm

Hey sorry I was really confused. I can see that it doesn't make any sense. Thank you for your time and patience though!

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)