On Mon, Jun 28, 2010 at 07:36:45PM +0530, Jeffrey Jose wrote: > experience I've never found a document which portrays Twisted as an > answer for I/O concurrency problems.
Seriously? Perhaps you were not looking for I/O Concurrency in the first place but where trying to use Reactor model for other purposes. > Twisted is not to parallelize I/Os but it has come to me as a framework that > lets you write event driven code. Yeah, one can do that. But the entire architecture, the 'Protocol' model has its inclinations towards Networking, isn't it. > No matter what you do, you will write blocking code in Python, but > that's where Twisted comes for rescue. It helps you abstract how a > particular blocking function is executed - maybe its threads, maybe > its processes. > Dont get me wrong, I'm not trying to say Twisted doesnt solve I/O problems, > maybe it does. But in my expeditions (I/O was never a problem for us) > I never used Twsited that way. It was more for Network communication and > serving requests. When we are taking about I/O aren't we talking about Network I/O. We surely are not talking about Database Read/Write, a yeah Database Server can also use the Reactor pattern with event driven code. -- Senthil Windows for Workgroups: Why crash 1 when you can crash 6? _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
