VbAsyncSocket VS Socket.io

I wonder if it is possible to make https://github.com/wqweto/VbAsyncSocket compile on Visual Basic 4, then you could target 16 bit.

What is impressive (or hilarious) is that someone opened an issue because it wasn't compatible with VB5[0]. The maintainer added a VB5 branch which apparently fixed the issues.

[0] https://github.com/wqweto/VbAsyncSocket/issues/4

You are right.

What is a good idea however, is to implement a TLSv1.3 library in Visual Basic 6[1], that doesn't have any external dependencies, by embedding machine code for AES encryption generated with MSVC in the source code, that you patch into memory at runtime, by using all sorts of tricks to do things in VB6 that you aren't supposed to do in VB6. Yes, that VB6, that was released in 1998, superseded by VB.NET in 2002. Because Microsoft has just announced it's supported on Windows 11.[2] So when developing new software, why not use something future-proof?

[1] https://github.com/wqweto/VbAsyncSocket

[2] https://docs.microsoft.com/en-us/previous-versions/visualstu...

After a quick Google Search, I found this: VbAsyncSocket

Anyway, that link for VB6 looks poromising: https://github.com/wqweto/VbAsyncSocket - it is using calls to ws2_32,dll, so it is up to date. I'll dust off VB6 to see how it works in that version, before I try to use it with VBA. VBA is not quite the same as VB6, very similar language, but not all of the same features can be implemented.

The first is the script tag in the head of our HTML document that loads the Socket.IO client library. This script tag includes the Socket.IO client library that will communicate with our socket.io server from the code above.

Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin.

Socket.io Docs

Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts under the services folder.

Hi I made a chat app using socket.io it worked fine locally but when i deployed the app on render.com socket is not working properly i have to refresh the page to see new messages please help...

Nextjs + socket.io.. Planning to use webrtc for video calls later

Implementação em Node usando Socket.io

I am using socket.io for real-time notification service. Previously my frontend part was deployed in Netlify and here the notification was not working properly as Netlify follows serverless architecture.

yes. Im running on DreamCompute currently. Discord.js and socket.io within same app. A dedicated server works too, but pricier.

No, not a library. More like, the frontend and backend just happen to need the same version to be compatible (socket.io is a good example, moment.js was the most basic I could think of).