Eric Faurot wrote:
So, I'd like to ask twisted enthiusiasts with better knowledge and experience of J2EE than I have, if they could provide meaningful points for advocating python/twisted over J2EE, pro and cons for each.
Let me take a shot. Pros for J2EE over Twisted: J2EE is fully mulithreaded and Twisted running on Python has some small built-in inconvenience named a "global interpreter lock" J2EE is built on Java which does not comply with the Open Source license requirement where Twisted on Python is Open Source compatible Pros for Twisted over J2EE: J2EE is fully mulithreaded and Twisted running on Python uses the event-driven model in a single thread J2EE is a full fledged application server platform where Twisted is good for network based applications J2EE is built on Java which does not comply with the Open Source license requirement where Twisted on Python is Open Source compatible
My main argument so far is that I am *way* more fluent in python,
I'm also much better at swinging a chain saw than chopping small with my swiss army knife. But I don't open cans with my chain saw just as I don't try to chop down trees with my swiss army knife :-) regards, Eugene Coetzee