NodeJS and socket.io ( Just Wondering )

[fdgfdgfdg]

Also very interested in this feature for fintech native app.

[niam]

Waiting for this feature also.

[AdrianoLuiz]

@s.alpaslan

I need to use real-time data in the project that I will start shortly. When will we be able to test realtime data with socket.io

Currently developing a virtual auction a need this

[Max_Saravia]

Hi, yeah, I hope the Wappler team can have this feature ready soon. Since Wappler introduced node.js into my life, I can’t stop thinking about all the things i’ll do in the near future. I’ve been playing around with Node a bit, but socket.io is what I really need to be able to move forward in new applications and make a really important difference to me to make the switch from php to Node.js. I know you are with mobile applications now guys, but please don’t forget about this important feature.

[patrick]

The socket.io package is already included with the node server but it will take a while until we have implemented it completely with Wappler.

We currently don’t have a user configuration and default it is not running. You can enable it by adding enableSockets: true to the config.json in the app/config folder. For now the only way to use the sockets server is by editing the sockets.js in the lib/setup folder, but we will update this file in the future and the file can be overwritten then.

[s.alpaslan]

Hello @patrick,

We have obtained very good results in our company application similar to the examples above. The completion of the integration will be exciting. Is there more time to integrate the UI with socket.io? because we think we will proceed faster and more confidently with the UI.

[PraneetB]

Hi Patrick,

We need this too. We’re building a CRM Application. The use-case is that it has to integrate with a call centre application (dialler).

Once a lead is dialled from the dialler, the dialler will call one of our APIs with the lead number and agentID (agent is logged into our CRM) and we need to be able to open a custom popup on the agent dashboard based on the agentID we receive.
(Happy to share more details on this)

UI for sockets would be game-changer for us for this use-case.

[s.alpaslan]

you can use sip client .

[AdrianoLuiz]

At the moment is what I need most Sokect.io

[s.alpaslan]

Is there an approximate time ?

[Teodor]

No, there’s no approximate time for this. When we have more news we will share them with you.

[patrick]

With the next update it will be easier to implement your own custom code for express middleware, sockets, formatters or writing your own modules. You can be placed in the app folder, so no need to edit the files in the lib folder anymore. I will create a topic after the release on how to implement your own custom code.

Implementation of sockets.io in wappler is still in the planning, will probably take a while till it is there. Have still a lot of work lying around.

[JonL]

@patrick

With the next update it will be easier to implement your own custom code for express middleware, sockets, formatters or writing your own modules.

Looking forward to this

[s.alpaslan]

Thank you very much for your quick response @patrick . This is good news. looking forward

[JonL]

I see you guys

[Max_Saravia]

I think socket.io implementation in Wappler could be a very nice christmas present … just saying …

[JonL]

[s.alpaslan]

hello @patrick ,

Will rooms and namespace be added for socket.io? It will also be nice to use with flow component. I think currently we can broadcast only to all clients .

@patrick

It would be like with the routes, it will auto generate the listeners to listen to a specific message in some specific namespace and execute a flow when it receives the a message.

Here a sample, it is just an idea, there is no implementation at this moment. We would have some json that defines the endpoints like:

[George]

Yes that is the next step

[mgaussie]

Next week’s update and another Christmas Present?