🚀 go-pugleaf

Thank you Remy(TeamB) for your reply.

Yes, I saw there are some Indy components in BCB6, but didn't see ones for 
POP3 and SMTP, unless I didn't see them!  (Being a total Indy novice I could 
easily pass over the relevant components.)

There being 3 versions of Indy around, 8, 9 & 10, how do they interrelate 
from the point of view of upwards compatibility?  How will a future Indy 11 
fit into this progression?

Given that -
    >  Now Indy 10 is the actively developed version, an it's C++ support 
will
    > (hopefully) finally be ready within the next month.,
do I correctly infer you are telling me to wait until about Jan06 before I 
start to try to install Indy 10 into my BCB 6?  Also at that time could 
there be a developed Install (or tested set instructions for the same) with 
the 'C++ support' mentioned as I do feel very uncertain about doing this 
after reading the various posts related to Indy installations.?  The problem 
lies in not having any exposure to Indy before now at all.

Thanks in advance,

Peter Evans.



"Remy Lebeau (TeamB)"  wrote in message 
news:438b43f6$1@newsgroups.borland.com...
>
> "Peter Evans" wrote in message
> news:4387b7e9$1@newsgroups.borland.com...
>
>> If NetMaster have been known to be pretty bad for sometime,
>> there has been time to do something about it, i.e., pick it up and
>> get it sorted out with another supplier or change to someone else's
>
> They did exactly that - BCB 6 shipped with Indy to replace NetMasters as 
> the
> primary internet component suite.  It is just that at the time BCB 6
> shipped, Indy 9 was not ready yet, so BCB 6 shipped with Indy 8 instead.
> Indy 8 is no longer supported by Indy's developers.  That is why I 
> mentioned
> that Indy's website has upgrade instructions for installing Indy 9 into 
> BCB
> 6.  Now Indy 10 is the actively developed version, an it's C++ support 
> will
> (hopefully) finally be ready within the next month.
>
>> keeping where possible as much of the syntax as is reasonable.
>
> That is usually not possible when changing to a new component supplier.
> Every author does things differently from other authors.
>
>
> Gambit
>
>