Boost logo

Boost :

From: Don G (dongryphon_at_[hidden])
Date: 2005-04-13 22:35:21

Hi Michel,

> IOCP provides the most scalable way to do I/O on
> Windows NT and later and it will blow the sock off
> just about anything it minimizes context switching
> by activaiting threads in FIFO order keeping a
> single thread hot, and blocks dequeing completions
> if there are more runnable threads on the port than
> cpus in the machine. Any serious server application
> should consider using it. But having a solid
> portable select based mechanism to fall back on
> could be used on any platform (supporting BSD
> sockets at least).

Sounds like it should, but it would be "easy" to measure down the
line and verify.

> Anyways maybe we should settle for the requirements,
> before we decide the details,

Agreed. The requirements are the hard part and important to agree

> but preferably I think the interface shouldn't rule
> out an IOCP based implementation.

There is nothing in the interface I proposed that would prevent an
ICOP implementation.

> And there seems to be a lot of different opinions on
> what kind of servers and scalability requirements
> the interface should provide. From simple blocking
> to full blown asynch with best implentation on any
> given plattform.

Quite a diversity :)


Do you Yahoo!?
Make Yahoo! your home page

Boost list run by bdawes at, gregod at, cpdaniel at, john at