I'm trying to use the latest V5 BETA in C++Builder 2006.
I get:
[C++ Error] Httpcontcod.hpp(87): E2347 Parameter mismatch in read access
specifier of property Active
Full parser context
HttpProt.hpp(25): #include
C:\AlC_BuilderComponents2006\ICSV5\Delphi\Vc32\Httpcontcod.hpp
Httpcontcod
Paul wrote:
> So I have to use ThreadDetach bor both TWSocket and HttpCli ?
No, just call HttpCli.ThreadDetach which also calls ThreadDetach
on the underlying TWSocket instance.
Just to show you the problem (V6):
procedure TCustomWSocket.ThreadDetach;
begin
if (GetCurrentThreadID = DWORD(FTh
So I have to use ThreadDetach bor both TWSocket and HttpCli ?
Paul
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Sent: Monday, August 14, 2006 5:07 PM
Subject: Re: [twsocket] SetThreadDesktop with ICS
> Arno Garrels wrote:
>> Paul wrote:
>>>
Arno Garrels wrote:
> Paul wrote:
>> That means I have to free all http clients, switch to a new desktop
>> and recreate everything, and continue the existing communications !
>> Nearly impossible.
>> Is there no other way to do this ?
>
> You may try to call ThreadDetach instead which destroys TW
Paul wrote:
> That means I have to free all http clients, switch to a new desktop
> and recreate everything, and continue the existing communications !
> Nearly impossible.
> Is there no other way to do this ?
You may try to call ThreadDetach instead which destroys TWSocket's
hidden window in V5.
Hello,
If the client comes into the state wsConecting then after a while some
event should fire. It can be the OnSessionConnected with or without a
winsock error or the onSessionClosed with or without a winsock error.
Please check both. Whith that information we could help more I think.
---
Rgds
That means I have to free all http clients, switch to a new desktop and
recreate everything, and continue the existing communications !
Nearly impossible.
Is there no other way to do this ?
Paul
- Original Message -
From: "Arno Garrels" <[EMAIL PROTECTED]>
To: "ICS support mailing"
Se
Paul wrote:
> Hi,
>
> a bit off topic, but I have problems using SetThreadDesktop() api.
> It returns error 170 = The requested resource is in use.
> Is this because ICS uses hidden windows ?
The online help seems to confirm that.
This function will fail if the calling thread has any windows or
Hi,
a bit off topic, but I have problems using SetThreadDesktop() api.
It returns error 170 = The requested resource is in use.
Is this because ICS uses hidden windows ?
Paul
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/
Hi,
No, the client does not generate any winsock error.It just gets disconnected
and even if I try connecting it again after the second send command to create
notification channel it shows its state as wsconnecting and does not connect
No clue where am i going wrong???
Wilfried Mestda
Hello,
When the client close, does is generate a winsock error ? Same question
for the datasocket at server side?
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Monday, August 14, 2006, 11:38, S S wrote:
> Hello Everyone,
> I have two
Hi, are there any requirement for running the app? I can open it all right
but after some seconds I get a Windows "Send Report" kindah error Very
interesting tool, I'd like to test it ...
Cheers,
Marcelo Grossi
- Original Message -
From: "David A. G." <[EMAIL PROTECTED]>
To: "TWs
Hello Everyone,
I have two units -
1)CAENUnit
2)MainUnit
There is a button "Start Server" in my main unit which when clicked starts my
server,starts my client,thereby on session connected event the client sends
commands to the reader to create notification channel ,receives reply
Hello Everyone,
I have two units -
1)CAENUnit
2)MainUnit
There is a button "Start Server" in my main unit which when clicked starts my
server,starts my client,thereby on session connected event the client sends
commands to the reader to create notification channel ,receives reply
Hello,
Yesterday I added NTLM support to the TSmtpCli, and it's
working fine against Exchange 2003 Service Pack 2.
Was no big deal since Francois already did the basic
work, see NtlmMsgs.pas.
I've uploaded new SmtpProt.pas/OverbyteIcsSmtpProt.pas
as well as matching demo DFMs since items in the
15 matches
Mail list logo