Article View: borland.public.cppbuilder.nativeapi
Article #4535Re: Detecing origin of messages
From: Bruce Salzman
Date: Wed, 04 Jan 2006 14:33
Date: Wed, 04 Jan 2006 14:33
6 lines
1040 bytes
1040 bytes
I'm not sure if this will help you, but you can associate an id with a thread using SetMessageExtraInfo() that you can retrieve with GetMessageExtraInfo(). -- Bruce
Technical Details
Message-ID:
<43bbdc2c@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news4.google.com!news2.volia.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<43badac9$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,7cb7d06378521605 X-Google-Attributes: gid10cc67,public X-Google-Language: ENGLISH,ASCII-7-bit From: " Bruce Salzman" <bruce@nospam.org> Newsgroups: borland.public.cppbuilder.nativeapi References: <43badac9$1@newsgroups.borland.com> Subject: Re: Detecing origin of messages Date: Wed, 4 Jan 2006 08:33:17 -0600 Lines: 8 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2670 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-RFC2646: Format=Flowed; Response NNTP-Posting-Host: 24.94.228.231 Message-ID: <43bbdc2c@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1136385068 24.94.228.231 (4 Jan 2006 06:31:08 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news4.google.com!news2.volia.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail