Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Moving away from Indy10



Permlink Replies: 4 - Last Post: Apr 9, 2018 9:59 AM Last Post By: Remy Lebeau (Te...
Colin Maharaj

Posts: 122
Registered: 12/2/99
Moving away from Indy10
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 14, 2018 6:48 AM
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.

I work with customers that I make TCP connections to their equipment and never
works properly in Indy10. This is affecting my sales and customer confidence.

I heard that there maybe newer networking libraries in the latest BCB compiler
based on Win10.
I did see the product manager do a demo, but cant find the video anymore.

Also is it possible to mix Indy9 and 10 in the same BCBXE4 compiler, so I
can fall back to indy9 for the modules in question.

Thanks....

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Goran Ekstrom

Posts: 149
Registered: 1/10/04
Re: Moving away from Indy10
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 14, 2018 8:05 AM   in response to: Colin Maharaj in response to: Colin Maharaj
IPWorks Builder Edition is available from GetIt. Don't know from what Builder version it was introduced.
Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Moving away from Indy10
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 14, 2018 8:14 AM   in response to: Colin Maharaj in response to: Colin Maharaj
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)
Colin Maharaj

Posts: 122
Registered: 12/2/99
Re: Moving away from Indy10
Click to report abuse...   Click to reply to this thread Reply
  Posted: Apr 8, 2018 11:44 AM   in response to: Colin Maharaj in response to: Colin Maharaj
Getting closer....

http://bcbjournal.org/forums/viewtopic.php?f=5&t=879

<excerpt>
My otherwise reasonably pleasent life with BDS 2009 C++ and a major multithreading
program is being made miserable with random reports from codeguard about my program
being out of memory (it is not!). I suspect the issue is really codeguard and
multi-threading but since most of the locations where the reports originate
are associated with AnsiStrings I thought........
</excerpt>

I am actually getting this with BCB6 on Win7 and BCBXE4 on Win7.
Note that codeguard for BCBXE4 does not work in Win10.

It could be that some of the TCP routines that use AnsiString in Indy Clients
are a problem if it is used in a thread and all my TCP routines are encapsulated
in threads.

This however does not prove yet that Indy Clients without codeguard in a thread
is unstable, which is what my argument is, and sorry, but I have still to write
a code sample to demonstrate the issues, but I am busy saving the sales team
who are on the front line.


On 3/14/2018 9:48 AM, 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.

I work with customers that I make TCP connections to their equipment and never
works properly in Indy10. This is affecting my sales and customer confidence.

I heard that there maybe newer networking libraries in the latest BCB compiler
based on Win10.
I did see the product manager do a demo, but cant find the video anymore.

Also is it possible to mix Indy9 and 10 in the same BCBXE4 compiler, so I
can fall back to indy9 for the modules in question.

Thanks....

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Remy Lebeau (Te...


Posts: 9,447
Registered: 12/23/01
Re: Moving away from Indy10
Click to report abuse...   Click to reply to this thread Reply
  Posted: Apr 9, 2018 9:59 AM   in response to: Colin Maharaj in response to: Colin Maharaj
Colin Maharaj wrote:

I am actually getting this with BCB6 on Win7 and BCBXE4 on Win7.
Note that codeguard for BCBXE4 does not work in Win10.

CodeGuard has never worked correctly, in ANY version. That is why I
avoid it like the plague.

It could be that some of the TCP routines that use AnsiString in Indy
Clients are a problem if it is used in a thread

Nope. AnsiString works just fine in threads.

--
Remy Lebeau (TeamB)
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02