I'm looking at a DLL that works as a wrapper for Winsock. One of the conditions for using the DLL is the COM. I'm not sure what this means. Looks like it's compatible with most other programming languages.
Post by Chris Iverson on Jul 12, 2019 17:20:46 GMT -5
There is a very convoluted indirect method that's been used before, but it requires a lot of work to adapt to any COM interface.
Quite frankly, it'd be easier to attempt to write direct Winsock code in LB than it would be to work with COM directly.
May I ask what is you're trying to do with Winsock? Because I've been busy writing a DLL specifically for LB to do TCP sockets and TLS encrypted sockets.
I'm also considering adding UDP functionality to the DLL, although not DTLS, since I think that's only supported on very current versions of Windows 10.
If there's something that can't be handled by my DLL, and can't be easily integrated into my DLL, the simplest way would probably be a custom LB DLL wrapper for the COM wrapper. Clunky, but it'd be far easier to use in LB.
In this case I was just curious if LB had that capability.
But the DLL you are writing, it would be great if it provided an easy method for UDP.
I did manage to find a way to get UDP to work by searching the older messages on the LB Yahoo group, but haven't tested it much. I'm not trying to write anything very serious. I work with some specialized equipment and simple strings can be sent over UDP to program the equipment.