-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Mar 16, 2010 at 01:19:01PM -0400, Frank Cusack wrote:
[...]
> And when you don't want to block on I/O. Threads are almost always
> easier than AIO, and especially easy (ie, no scary complexity issues
> eg deadlock) if you aren't sharing data structures.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Such a little phrase... ;-)
Yes, if you aren't sharing data structures you may as well use separate
processes.
Honestly, I do prefer the explicit complexity of async IO to the
implicit complexity of locking. At least in IO-centered server
processes. Threads just /seem/ easy.
And as to the latency/performance, watch the small/fast HTTP servers
moving to async IO models.
I'm not the one to be taken too seriously on it, but I feel that Timo
has the right hunch here.
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFLoJjjBcgs9XrR2kYRAlz+AJ9J1m3GiX8xAXyIyRa/2yyvejfc0QCdEhLy
an2q0IxgRP/FYp4gVda/22Q=
=exbZ
-----END PGP SIGNATURE-----
