Albert, do you really need multithreadness with ICS? It's asynchronous so
you just need one additional thread that will launch and control all
sockets.
That's what I'm doing... just one additional thread for the HTTP requests. I
don't have a thread for every HTTP request.
And regarding the
Hi Arno,
Yes, it works.
What does that mean?
It mostly works as it seems to work properly, but I suppose the devil is
in the details... there may be hidden issues that are not coming up yet or
not making themselves known (yet).
I have a a message loop for the main thread...
Then it
Hello Albert,
On Fri, Mar 11, 2011 at 5:48 PM, Albert Wiersch
supp...@htmlvalidator.comwrote:
Also, I use a TMemoryStream with some objects. Is that an issue? Is it
thread safe to have multiple HttpClip objects using multiple TMemoryStreams
at the same time?
No it's not thread safe. It
It is safe to have each HttpCli using his own TMemoryStream and have a lot
of HttpCli running concurrently.
It is unsafe to have the same TMemoryStream used by several HttpCli
components unless you know exactly what you are doing. I would not
recommand
it.
Great. I was hoping that was the
Albert, do you really need multithreadness with ICS? It's asynchronous so you
just need one additional thread that will launch and control all sockets.
And regarding the leaks, consider using FastMM4 in full debug mode to get more
info (i.e. type of variable that has been leaked).
Albert Wiersch wrote:
All threads must have a message loop otherwise ICS won't work.
Yes, it works.
What does that mean?
I have a a message loop for the main thread...
Then it is well prepared for ICS.
I
support the same message loop is used for the threads created from
that thread.
