Comments on: From 0.62 to 0.70 http://laurentszyster.be/blog/from-062-to-070/ Python on Peers Sat, 04 Feb 2012 05:55:37 +0000 http://wordpress.org/?v=1.5.1.3 by: Laurent Szyster http://laurentszyster.be/blog/from-062-to-070/#comment-2340 Thu, 10 Aug 2006 17:20:43 +0000 http://laurentszyster.be/blog/from-062-to-070/#comment-2340 Hi Toothy, Indeed writing an Allegra based application web server makes sense. Actually there is one cooking in SVN, it's called PRESTo: http://svn.berlios.de/svnroot/repos/allegra/lib/presto_http.py However, even if it is possible, adding a WSGI interface to support Django and other LAMPython web framework in replacement of Apache of Cherokee makes little sense to me. Because the LAMP model for web application is a "synchronous share-nothing" design. Django applications would not perform faster or scale up higher with Allegra (rather the contrary, they'll have to suffer from a slower implementation of HTTP/1.1 than the one Apache provides and which is allready made of optimized C code). Using the Django stack would require to thread each request handler and force them to access the asynchronous API through a single contention point, loosing all of the benefits expected from Allegra's asynchronous model. Allegra was designed first for web application *peers*. The framework is intended to provide a cross-portable web stack that must fit small network appliances or a crowded desktop. It *could* eventualy compete against Zope and the "synchronous share-everything" designs of J2EE. But for that to happen, Allegra will first have to become stable enough to be profitable for entreprise application developers. Only time will tell if Allegra will put Python on every Peers. <p>As you can see from Allegra's relatively slow progress, it's been developed by a perfectionnist without deadlines ;-) Regards,</p> Hi Toothy,

Indeed writing an Allegra based application web server makes sense.

Actually there is one cooking in SVN, it’s called PRESTo:

http://svn.berlios.de/svnroot/repos/allegra/lib/presto_http.py

However, even if it is possible, adding a WSGI interface to support Django and other LAMPython web framework in replacement of Apache of Cherokee makes little sense to me.

Because the LAMP model for web application is a “synchronous share-nothing” design. Django applications would not perform faster or scale up higher with Allegra (rather the contrary, they’ll have to suffer from a slower implementation of HTTP/1.1 than the one Apache provides and which is allready made of optimized C code). Using the Django stack would require to thread each request handler and force them to access the asynchronous API through a single contention point, loosing all of the benefits expected from Allegra’s asynchronous model.

Allegra was designed first for web application *peers*.

The framework is intended to provide a cross-portable web stack that must fit small network appliances or a crowded desktop.

It *could* eventualy compete against Zope and the “synchronous share-everything” designs of J2EE. But for that to happen, Allegra will first have to become stable enough to be profitable for entreprise application developers.

Only time will tell if Allegra will put Python on every Peers.

As you can see from Allegra’s relatively slow progress, it’s been developed by a perfectionnist without deadlines ;-)

Regards,

]]>
by: ToothyByte http://laurentszyster.be/blog/from-062-to-070/#comment-2338 Thu, 10 Aug 2006 16:08:53 +0000 http://laurentszyster.be/blog/from-062-to-070/#comment-2338 Laurent, I don't know if that is even possible/feasible or whether it makes sense for you to do. But if you were a write an Allegra based webserver that would say replace the default (builtin) webserver in Django (wich is based on BaseHTTPServer) it would blow people's mind ... you'd instantaneously put Allegra into the mainstream. That web framework is fast growing, I posted a simple example on my site generated over 4000 hits in two days ... I wish I knew where to start doing what I suggest above ... no enough experience in makeing webservers Laurent,

I don’t know if that is even possible/feasible or whether it makes sense for you to do.

But if you were a write an Allegra based webserver that would say replace the default (builtin) webserver in Django (wich is based on BaseHTTPServer) it would blow people’s mind … you’d instantaneously put Allegra into the mainstream.

That web framework is fast growing, I posted a simple example on my site generated over 4000 hits in two days … I wish I knew where to start doing what I suggest above … no enough experience in makeing webservers

]]>