Article View: borland.public.cppbuilder.internet.socket
Article #2662Re: Problem with Indy Client (TIdHTTP)
From: hamid
Date: Tue, 07 Mar 2006 09:57
Date: Tue, 07 Mar 2006 09:57
96 lines
3091 bytes
3091 bytes
This is the version of the BDS 2006 that I am using:
Borland® C++Builder® Preview for Microsoft® Windows™ Version 10.0.2151.25345 Copyright © 2005 Borland® Software Corporation. All Rights Reserved.
The version of the indy components, IndyCore100.bpl, IndyProtocols100.bpl, and IndySystem100 is 10.0.0.17.
As for lines number, I wonder what's wrong with my Idwinsock2.hpp because it includes more than 2200 lines.
Moreover, I added the lines below to temporarily solve the problem.
// hamid - start
#pragma pack(push,1)
struct TWSAProtocolChain
{
public:
int ChainLen;
int ChainEntries[7];
} ;
#pragma pack(pop)
#pragma pack(push,1)
struct TWSAProtocol_InfoA
{
public:
int dwServiceFlags1;
int dwServiceFlags2;
int dwServiceFlags3;
int dwServiceFlags4;
int dwProviderFlags;
#pragma pack(push,1)
GUID ProviderId;
#pragma pack(pop)
int dwCatalogEntryId;
#pragma pack(push,1)
TWSAProtocolChain ProtocolChain;
#pragma pack(pop)
int iVersion;
int iAddressFamily;
int iMaxSockAddr;
int iMinSockAddr;
int iSocketType;
int iProtocol;
int iProtocolMaxOffset;
int iNetworkByteOrder;
int iSecurityScheme;
int dwMessageSize;
int dwProviderReserved;
char szProtocol[256];
} ;
#pragma pack(pop)
#pragma pack(push,1)
struct TWSAProtocol_InfoW
{
public:
int dwServiceFlags1;
int dwServiceFlags2;
int dwServiceFlags3;
int dwServiceFlags4;
int dwProviderFlags;
#pragma pack(push,1)
GUID ProviderId;
#pragma pack(pop)
int dwCatalogEntryId;
#pragma pack(push,1)
TWSAProtocolChain ProtocolChain;
#pragma pack(pop)
int iVersion;
int iAddressFamily;
int iMaxSockAddr;
int iMinSockAddr;
int iSocketType;
int iProtocol;
int iProtocolMaxOffset;
int iNetworkByteOrder;
int iSecurityScheme;
int dwMessageSize;
int dwProviderReserved;
WideChar szProtocol[256];
} ;
#pragma pack(pop)
typedef TWSAProtocol_InfoA *PWSAProtocol_InfoA;
typedef TWSAProtocol_InfoW *PWSAProtocol_InfoW;
struct _TRANSMIT_FILE_BUFFERS;
typedef _TRANSMIT_FILE_BUFFERS *PTransmitFileBuffers;
// hamid - end
Technical Details
Message-ID:
<440d6719$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!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>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,bd43561adb272318 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,UTF8 From: "hamid" <hrz_mir@yahoo.com> Sender: "hamid" <hrz_mir@yahoo.com> Reply-To: "hamid" <hrz_mir@yahoo.com> Subject: Re: Problem with Indy Client (TIdHTTP) Newsgroups: borland.public.cppbuilder.internet.socket X-User-Info: 80.75.8.69 X-Forwarded-For: 172.16.1.5 References: <440ad603$1@newsgroups.borland.com> <440c7ea8$1@newsgroups.borland.com> <440c8f53$1@newsgroups.borland.com> <440caf6b$1@newsgroups.borland.com> NNTP-Posting-Host: 207.105.83.66 Message-ID: <440d6719$1@newsgroups.borland.com> Date: 7 Mar 2006 02:57:29 -0700 X-Trace: newsgroups.borland.com 1141729049 207.105.83.66 (7 Mar 2006 02:57:29 -0700) Lines: 98 Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail