Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Jan : [Q] The future of TCustomWinSocket Delphi 2006 and beyond?

www.cryer.info
Managed Newsgroup Archive

[Q] The future of TCustomWinSocket Delphi 2006 and beyond?

Subject:[Q] The future of TCustomWinSocket Delphi 2006 and beyond?
Posted by:"Donovan J. Edye" (donovan_nospam@namsys.com.au)
Date:30 Jan 2007 17:00:35

G'Day,

- I have a large amount of existing code based on an internal self
written library that makes use of TCustomWinsSocket (blocking with
custom internal threads to handle read and write) and descendants (ie
TClientSocket, TServerSocket). I also have other code that is based on
Indy 8.
- I am now converting things to Delphi 2006 from Delphi 6. And as Indy
has jumped from 8 (Delphi 6) to 9 or 10 (Delphi 2006) I am weighing up
how to proceed from here.
- My preference would be to stay with TCustomWinSocket as I only have
to support Win32 VCL and I know the code works and is robust. Indy has
had a paradigm shift from v8 to v10 so there is some work in reworking
any Indy code. Added to that the Indy Project web site is very short on
news as the RSS / Blogs don't get updated regularly (The project site
has always been "slack" in terms of keeping current)

So my questions are as follows:

1. Should I continue with TCustomWinSocket? Is it being deprecated by
Borland/Codegear? Its there in Delphi 2006 and the help does not say
anything about it being phased out but.....
2. What are the compelling reasons to go to Indy over TCustomWinsocket
for core socket comms ie. No protocol support etc.

TIA

--
--Donovan

Replies:

www.cryer.info
Managed Newsgroup Archive