OK, to be clear. Twisted doesn’t do anything about cpu bound tasks and for good reason. there’s no way to make a compute bound job go any quicker by reordering subtasks; the only thing you could possibly do is add more compute resources; and even that wouldn’t work out in python because of a subtlety … Read more
As long as the two messages were sent on the same TCP connection, order will be maintained. If multiple connections are opened between the same pair of processes, you may be in trouble. Regarding Twisted, or any other asynchronous event system: I expect you’ll get the dataReceived messages in the order that bytes are received. … Read more
Twisted is more mature — it’s been around for a long, long time, and has so many bells and whistles as to make your head spin (implementations of the fanciest protocols, integration of the reactor with a large variety of other event loops, and so forth). Node.js is said to be faster (I have not … Read more
There are at least two problems with OnionProtocol: The innermost TLSMemoryBIOProtocol becomes the wrappedProtocol, when it should be the outermost; ProtocolWithoutConnectionLost does not pop any TLSMemoryBIOProtocols off OnionProtocol‘s stack, because connectionLost is only called after a FileDescriptors doRead or doWrite methods return a reason for disconnection. We can’t solve the first problem without changing the … Read more
Let me tell you a few reasons that makes using MOM (Message Oriented Middleware) probably the best choice. Decoupling: It can decouple/separate the core components of the application. There is no need to bring all the benefits of the decoupled architecture here. I just want to point it out that this is one of the … Read more
The reactor pattern is more specific than “event driven programming”. It is a specific implementation technique used when doing event driven programming. However, the term is not used with much accuracy in typical conversation, so you should be careful about using it and expecting your audience to understand you, and you should be careful in … Read more
There are a lot of different aspects of Twisted that you might find cool. Twisted includes lots and lots of protocol implementations, meaning that more likely than not there will be an API you can use to talk to some remote system (either client or server in most cases) – be it HTTP, FTP, SMTP, … Read more
Look here: Twisted Web in 60 seconds. That’s a group of blog posts describing step by step how to do lots of common stuff with Twisted, all written by Jean-Paul Calderone, the biggest contributor of Twisted. It’s really where you should start. After that, look at the Twisted core documentation then refer to the API … Read more
For very small numbers of sockets (varies depending on your hardware, of course, but we’re talking about something on the order of 10 or fewer), select can beat epoll in memory usage and runtime speed. Of course, for such small numbers of sockets, both mechanisms are so fast that you don’t really care about this … Read more
It is very difficult to write code that is thread safe. With asyncronous code, you know exactly where the code will shift from one task to the next and race conditions are therefore much harder to come by. Threads consume a fair amount of data since each thread needs to have its own stack. With … Read more