BorlandTalk.com

Atle Smelvær · Guest

Is there any IOCP server implementation in Delphi? I know that Indy10 will
have this functionality, but at this point IOCP inside Indy is not working
as it should, and I'm sure that it will be a long time before they release a
final Indy10 since there are still mutch do before it's finished. Also, I'm
using Indy9 on other projects, and it is not possible to have both installed
without a lot of rewriting inside Indy10.

I've looked on the internet but found nothing, so now I'm making an IOCP
server. But if there is any components out there at a reasonable price, it
would cost me less in time spend developing this piece.

Anyone of you who have made a good IOCP server, or knows about one. The
sourcecode must be available.

-Atle

Chad Z. Hower aka Kudzu · Guest

"Atle Smelv r" <atle (AT) datagrafikk (DOT) no> wrote in
news:4030e02b (AT) newsgroups (DOT) borland.com:

Martin James · Guest

Lukas Gebauer · Guest

Atle Smelvær wrote:

Chad Z. Hower aka Kudzu · Guest

"Martin James" <mjames_falcon (AT) dial (DOT) pipex.com> wrote in
news:4030ee4f (AT) newsgroups (DOT) borland.com:

Zinvob · Guest

Ok. I see that I've not done enough research here before I say something :)

I'll look into it. Do you have a link to Indy in depth, where parallell
installs of Indy9 and Indy10 is covered.

Thanx for your info.

-Atle

Chad Z. Hower aka Kudzu · Guest

"Zinvob" <zinvob (AT) sdf (DOT) lonestar.org> wrote in news:40310c45
@newsgroups.borland.com:

Atle Smelvær · Guest

Why is the indy10.zip removed from the CSV archive, I would like to have the
newest version, not a backup from last year?

-Atle

Atle Smelvær · Guest

I just wondered how your worker threads are built inside Indy10. The server
I was creating, had a self growing worker pool. Each time a worker thread
was starting to read or send a message, an IdleThreads counter was
decremented, and a WorkingThreads counter was incremented. When a client
decremented the IdleThreads, it also checked if it's reached zero. When zero
is reached, it creates another WorkerThread before continuing. This way, you
never freeze the server when heavy actions are done on some of the threads,
still keeping the thread count as low as possible. When the worker thread
was going into idle state again and idle threads was to be incremented, it
finished itself if idle threads already was 2*cpus on system. IOCP is
perfect for this kind of worker threads.

-Atle

Atle Smelvær · Guest

One more question. Is there a threadsafe way to send packets and disconnect
outside the read thread in Indy10?

Thanx

-Atle

Martin James · Guest

My approach is to just create another handler thread if one is needed *and*
the queue of free handler threads is empty. The create has to be done
sometime, so why not so it as required? If you create a spare thread just
when the queue becomes empty, and you do not know if another will be needed
will this not create a thread too far?

Rgds,
Martin

Atle Smelvær · Guest

Since IOCP works with GetQueuedCompletionStatus, you need to have a thread
waiting on this API call. That's why a new thread is created at once. By
doing this I make sure that there's always one thread waiting on a
CompletionStatus, ready to start working if something happens. Once the
other thread is finished, it will always clean up itself if the amount of
needed idle threads are intact.

willy Chandra · Guest

hi Atle,
i think you should check the IOCP Classes in sourceforge. there is 1 project written in Delphi + IOCP

ciaoo Willy

"Atle Smelvær" <atle (AT) datagrafikk (DOT) no> wrote:

Chad Z. Hower aka Kudzu · Guest

"Atle Smelv r" <atle (AT) datagrafikk (DOT) no> wrote in
news:4031cad0$1 (AT) newsgroups (DOT) borland.com:

Chad Z. Hower aka Kudzu · Guest

"willy Chandra" <willy.chandra (AT) web (DOT) dot.de> wrote in
news:40324eda$1 (AT) newsgroups (DOT) borland.com: