Article View: borland.public.cppbuilder.internet.socket
Article #4452Re: Indy and WinSock2.h problem
From: Bob Gonder
Date: Tue, 08 Feb 2005 18:32
Date: Tue, 08 Feb 2005 18:32
10 lines
1406 bytes
1406 bytes
Remy Lebeau (TeamB) wrote: >> I need both Indy and BCB Sockets components in my project! > >Why? Indy does everything that Borland's native sockets do, and more. You >are better off not mixing multiple socket libraries together. Would it cause run-time conflicts if he used the 2 winsocks in different modules? Write Indy code in one, and Winsock code in another?
Technical Details
Message-ID:
<t51i01puq1d6d5v5h92h300b7d3eni27tm@4ax.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<4208eb0f@newsgroups.borland.com> <4208f629$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,107c7f042cb7cb6a X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: Bob Gonder <notbg@notmindspring.invalid> Newsgroups: borland.public.cppbuilder.internet.socket Subject: Re: Indy and WinSock2.h problem Date: Tue, 08 Feb 2005 10:32:55 -0800 Organization: MindSpring Enterprises, Inc. Reply-To: notbg@notmindspring.invalid Message-ID: <t51i01puq1d6d5v5h92h300b7d3eni27tm@4ax.com> References: <4208eb0f@newsgroups.borland.com> <4208f629$1@newsgroups.borland.com> X-Newsreader: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 67.77.147.252 X-Trace: newsgroups.borland.com 1107887573 67.77.147.252 (8 Feb 2005 10:32:53 -0800) Lines: 12 Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail