Fork with new features

[spawn451]

Hello everyone, you can check out my fork here.
I’ve made several updates and added new features, including:

• IPv6 support

• UDP support

• New threaded socket components

• Universal socket components with dual-protocol support and Thread pool processing

• TLS implementation for Windows platforms via SChannel integration

[c-michail]

It would be nice to have them on the main branch here.

Also OpenSSL 3.5 support and Quic (since you implement UDP) will be awesome

@DelphiBuilder could add a new Repository eg. NetCom8 adding the @spawn451 features along with OpenSSL 3.5 support.
Delphi implementations of OpenSSL 3.5 are all over the github.

[c-michail]

@spawn451 btw your UDP Server/Client misses the "Pro" versions which handle commands.

[spawn451]

@chmichael Thanks for the suggestion, indeed it would be good to have a lightweight custom command protocol for UDP.

[spawn451]

I added a lightweight protocol for UDP component to send command so now we have Raw + Command (with auto chunk for large data).

[c-michail]

btw, SChannel is only for windows so OpenSSL support is required for other OS

[spawn451]

I updated and refactor my fork,I think I will not push anymore update for now.

[c-michail]

Better build a Lock class which use TMonitor for compiler VER360 and up and TCriticalSection for lower compilers instead having to maintaining 2 separate sources.

[spawn451]

Yes, that makes sense ;-)

[c-michail]

@spawn451 The OnConnected/OnDisconnected events are missing from UDP components.

[spawn451]

I didn't implement this because UDP is a connectionless protocol

[c-michail]

I forgot about that ... Then i need to manually make a verification mechanism ....

[c-michail]

Indy has connect/disconnect on the UDP client side so how about adding keep alive on UDP components ? Then we can detect the disconnection. Eg sending an ICMP message every x seconds.

[BitmasterXor]

Indy has connect/disconnect on the UDP client side so how about adding keep alive on UDP components ? Then we can detect the disconnection. Eg sending an ICMP message every x seconds.

for UDP to have an OnConnect or OnDisconnect you would have to make some sort of socket polling technique that sends a data packet to initialize a "So called OnConnect" and the OnDisconnect would fire if the socket polling failed or something similar to that nature.

[c-michail]

Never looked but i wonder how QUIC handles this ...Maybe we can adopt QUIC mechanism