Mike Lenox wrote:
> That's good information. I am not surprised if the TTimer is mine.
> BUT, the issue is still that I only get the error when I have both ICS
> components running. This implies that they are somehow interacting.
Why don't you debug the application? I guess an exception or access
I will try my best to describe the problem I am experiencing a bit better;
My PHP side I have this:
On Dlephi side I have this:
var
aString1,aString2 : String;
begin
aString1 := HttpCli1.RcvdHeader.Values[xx: xx'];
aString2 := HttpCli1.RcvdHeader.Values[yy: yy'];
aLongString1 is very l
That's good information. I am not surprised if the TTimer is mine. BUT,
the issue is still that I only get the error when I have both ICS
components running. This implies that they are somehow interacting. Is
there any possibility of that or any past complaints of such behavior?
Arno Garrels w
> I guess I am not being very clear.
Indeed...
> I am not creating other threads. I only have one ... the main Delphi
thread.
Ah !
> I am creating different ICS components, a TTnCnx client and a
> TWSocketServer in separate parts of my application. There are no shared
> global variables and the
Mike Lenox wrote:
> BUT, the two objects seem to be interacting with each other as I get a
> TTimer access error ONLY when both objects are active and I make an
> actual connection to the server.
Both TWSocketServer and TTnCnx do not use a TTimer. If your code uses a
TTimer what is the event hand
I guess I am not being very clear.
I am not creating other threads. I only have one ... the main Delphi thread.
I am creating different ICS components, a TTnCnx client and a
TWSocketServer in separate parts of my application. There are no shared
global variables and the two instances are in di
>> > Is there a problem having multiple instances of ICS
>> > socket objects on the same thread?
>> Defenitely no problem.
>> The most frequent error when using ICS components in a thread is to
forget
>> you must create the component from with the thread's execute method. If
you
>> create the comp
> Francois Piette wrote:
> >> Regarding the hard coded boundary strings I suggest to
> >> make them (or parts) component properties.
> >
> > Would be a good idea to create a property XMailer with that string.
> > The default value would be the current value. Some trick should be
> > used so that th
In my current app, I only have a main thread. So, does this, "...this
may cause a lot of trouble", apply? I should expect trouble if I have
multiple ICS components all executing on the main thread?
Original Message
Subject:Re: [twsocket] Conflicts between multiple ins
Francois Piette wrote:
>> Regarding the hard coded boundary strings I suggest to
>> make them (or parts) component properties.
>
> Would be a good idea to create a property XMailer with that string.
> The default value would be the current value. Some trick should be
> used so that the correct com
Hi !
Sorry for slightly out of topic message, but this info could help you write
better programs using ICS.
Having a clear understanding how things are going under the cover always
help design better solutions.
Windows Internal Book will surely helps you. At least it helps me.
http://technet.micro
Hi Hoby,
> Specifically, the problem was that GoDaddy doesn't
> like parenthesis ["(" and ")"] in the "from" field.
Thanks for your feedback.
It is always good to know that the problem was not in ICS component.
--
francois.pie...@overbyte.be
Author of ICS (Internet Component Suite, freeware)
Aut
> Is there a problem having multiple instances of ICS
> socket objects on the same thread?
Defenitely no problem.
The most frequent error when using ICS components in a thread is to forget
you must create the component from with the thread's execute method. If you
create the component from the th
13 matches
Mail list logo
