Can Indy do non-blocking async I/O?

[Tony Leotta]

Does any body know if INDY can handle async or
non-blocking i/o?

The docs say it does just blocking i/o. I find this to
be a severe limitation.

[Justin Pitts]

> Does any body know if INDY can handle async or
> non-blocking i/o?

Nope.

> The docs say it does just blocking i/o. I find this to
> be a severe limitation.

Then it aint for you. try ICS

[Luke Croteau]

> The docs say it does just blocking i/o. I find this to
> be a severe limitation.

Well... It could be a severe limitation if it weren't for one thing... Indy
is designed to be blocking. Meaning the people who use Indy want/need
blocking.

'Nuff said.

-Luke

[John M. Jacobson]

It is only a limitation if you don't want to multithread your app. In such a
case, Francois Piette's ICS is what you want. If you go to my web site and
then to the links page, you will find the URL for his web site. ICS uses
non-blocking sockets. Just be forwarned that it is event-driven as a result,
so your code will be non-linear event-based code.

--
John M. Jacobson
Visit Jake's Delphi Page at http://www.xnet.com/~johnjac
Cycling to cure cancer - http://homepages.borland.com/jkaster/tnt/

"Tony Leotta" <to...@pillarsoftware.com> wrote in message
news:3b03f4d5$1_1@dnews...

[Tony]

Tony,
It is hardly a limitation. Blocking sockets work better in a lot of
situations, IE in messaging apps.
Indy also has the ability to set a timeout on your reads. and in 8.1 on
connnects.
Also it is way more intuitive to use standard Try Execpt blocks to handle
errors, in a async you have to do everthing including most error checking in
events.

Tony Caduto
Milwaukee WI

"Tony Leotta" <to...@pillarsoftware.com> wrote in message
news:3b03f4d5$1_1@dnews...