Colin Maharaj wrote:
For me, I moved from Indy9 to 10 and BCB6 to BCBXE4, and my TCP
Clients was never the same. Spent years trying to fix and never seem
to work like how Indy9 worked.
In what way exactly? Did you ever ask for Indy help before while
porting your app from 9 to 10?
I work with customers that I make TCP connections to their equipment
and never works properly in Indy10.
Again, in what way? Lots of people use Indy 10 successfully for their
TCP connections. Any problems you are having are likely to be related
to how you use it. There were some big fundamental paradigm shifts
from Indy 9 to 10, and even from earlier versions of 10 to later
versions of 10. Can you provide an example of something that is not
working for you?
I heard that there maybe newer networking libraries in the latest BCB
compiler based on Win10.
You might to thinking of things like TSocket and THttpClient:
http://docwiki.embarcadero.com/Libraries/en/System.Net.Socket.TSocket
http://docwiki.embarcadero.com/Libraries/en/System.Net.HttpClient.THTTPClient
THttpClient could be a good alternative to TIdHTTP, for instance. But
I wouldn't say TSocket is a good replacement for
TIdTCPClient/TIdTCPServer, as it is a pretty bare-bones socket
implementation, so you would likely end up recreating higher-levle
functionality that Indy already handles for you.
Also is it possible to mix Indy9 and 10 in the same BCBXE4 compiler
No. First off, because Indy 9 doesn't support modern compilers to
begin with. And second, because there are a lot of duplicate units and
classes in both libraries, even though they use different package
structures. If you really want to use both versions in a single app,
you are going to have to separate their uses into DLLs that your app
can then choose from at runtime. And that is likely to be an even
bigger rewrite of your app than simply porting from Indy 9 to 10
properly.
--
Remy Lebeau (TeamB)
Connect with Us