Article View: borland.public.cppbuilder.internet.socket
Article #2551Re: Problem with Indy Client (TIdHTTP)
From: Fred Hebert
Date: Sat, 25 Mar 2006 18:42
Date: Sat, 25 Mar 2006 18:42
52 lines
2736 bytes
2736 bytes
Hi Remy, I am very interested in the Indy support for the C++ personality of BCB2006. When Ininstalled BDS2006 I had an early version that did not warn about C++ compatibility of Indy 10 and I installed Indy 10. Now I am trying to update (actually a bug fix) in one of my apps. I am trying to move everything from BCB5 to BDS2006... Anyhow, I only need the IdHTTP client. I use this in my web update mechanism. If at least this is stable in the latest version of Indy 10 I think I will be OK. I need a quick fix. I either need to get Indy 10 working, or downgrade BDS2006 to Indy 9. Can you help, or at least point me to a procedure for downgrading to Indy 9? Any help would be greatly appreciated. Thanks in advance, Fred. "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote in news:4415e32f$1@newsgroups.borland.com: > > "hamid" <hrz_mir@yahoo.com> wrote in message > news:4412a9dc$1@newsgroups.borland.com... > >> I checked this website and found the components here: >> http://www.indyproject.org/Sockets/Download/Files/Indy10.en.iwp >> >> But as they mentioned, the only available version is 10.0.52 which is >> old. > > Please re-read that page again. That same page has the download link > for the latest "Development Snapshot". > >> Moreover, the prepared components have been designed in >> Delphi not BCB or BDS. > > Most third-party components in general are written in Delphi Pascal, > not C++. All version of BCB, and C++ for BDS, can use Delphi > components. > > > Gambit > > >
Technical Details
Message-ID:
<Xns97918B62FACFDfhebertfjhconsulting@207.105.83.66>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<440ad603$1@newsgroups.borland.com> <440c7ea8$1@newsgroups.borland.com> <440c8f53$1@newsgroups.borland.com> <440caf6b$1@newsgroups.borland.com> <440d6719$1@newsgroups.borland.com> <440dccba$1@newsgroups.borland.com> <440e820f$1@newsgroups.borland.com> <440eaa8a$1@newsgroups.borland.com> <4412a9dc$1@newsgroups.borland.com> <4415e32f$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,bd43561adb272318 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit Newsgroups: borland.public.cppbuilder.internet.socket Subject: Re: Problem with Indy Client (TIdHTTP) From: Fred Hebert <fhebert@nospam.fjhconsulting.com> References: <440ad603$1@newsgroups.borland.com> <440c7ea8$1@newsgroups.borland.com> <440c8f53$1@newsgroups.borland.com> <440caf6b$1@newsgroups.borland.com> <440d6719$1@newsgroups.borland.com> <440dccba$1@newsgroups.borland.com> <440e820f$1@newsgroups.borland.com> <440eaa8a$1@newsgroups.borland.com> <4412a9dc$1@newsgroups.borland.com> <4415e32f$1@newsgroups.borland.com> Organization: FJH Consulting Message-ID: <Xns97918B62FACFDfhebertfjhconsulting@207.105.83.66> User-Agent: Xnews/5.04.25 NNTP-Posting-Host: 68.11.125.170 Date: 25 Mar 2006 11:42:07 -0700 X-Trace: newsgroups.borland.com 1143315727 68.11.125.170 (25 Mar 2006 11:42:07 -0700) Lines: 53 Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail