flup 1.0 released

Monday, September 10. 2007

I resolved a few more outstanding issues with flup and decided to make a release. I went ahead and called it 1.0. And as I previously mentioned, I went ahead and removed the publisher and middleware modules.

If you've been following the Subversion repository for flup (which has been quiet due to my switching to Mercurial), there have only been 1 or 2 new fixes.

I also uploaded the tarball and 2.5 egg to the Cheese Shop. Further updates will also go to the Cheese Shop.

And on the subject of further updates, consider flup to be in maintenance mode - there won't be any more new development. Bug fixes and bug reports are still welcome, of course. (Though this has been the way I've run flup for quite a while now, so I'm just making a formal announcement.

)

And as a bit of editorializing, did I ever mention how much I hate FastCGI?

Around the time I first released flup, I had transitioned my apps from FastCGI to AJP, and I never missed FastCGI since. But much to my disappointment, the FastCGI module was the most popular... most likely due to ubiquitous & cheap shared hosting services (e.g. Dreamhost).

Oh well, I don't even use flup myself anymore. I've switched to ajp-wsgi...

Posted by Allan Saddi in flup at 16:59 | Comments (7) | Trackbacks (0)

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

Any idea where will go flup session ?

#1 wilk (Homepage) on 2007-09-14 11:07 (Reply)

It's still there in flup 0.5. I also made sure 0.5 was still available at the Cheese Shop (and my download directory). But I really don't want to support it anymore.

I strongly recommend migrating away from flup sessions. Perhaps to Beaker: http://beaker.groovie.org/

The usage is the same (but rather than the key "com.saddi.service.session", you use "beaker.session"). And you have to make sure you call session.save() whenever you modify the session.

#2 Allan Saddi (Homepage) on 2007-09-14 12:46 (Reply)

I am using django + flup.fcgi + lighttpd.

How to use AJP as you recommended?

#3 Henry (Homepage) on 2007-10-26 09:56 (Reply)

Interesting. Care to explain why you hate FastCGI? It seems to work fine for me.

#4 Jack on 2007-10-26 16:06 (Reply)

Beaker didn't work for me in conjunction with ajp-wsgi. I got the same session-id for different browsers. Can you give me an example for Beaker Session in conjunction with ajp-wsgi.

I'have documented my experiences at http://www.xhostplus.at/static/webpy-ajp-wsgi.html.

#5 Erwin (Homepage) on 2008-03-24 02:25 (Reply)

I use Beaker and ajp-wsgi pretty extensively and I haven't run into any problems like you've described. The frameworks I use with the two are Pylons, Flannel, or sometimes no framework at all (e.g. an authentication middleware component that just requires sessions).

The issue could be with web.py or with mod_jk, as these are the 2 major differences between our configurations. (I use Apache 2.2's mod_proxy_ajp.) Though I don't see how mod_jk could really affect this.

Have you tried web.py + Beaker on another WSGI server? I'm a bit suspicious about the way session.save() is being called in web.py. And like you mentioned, the non-web.py example worked fine.

#6 Allan Saddi (Homepage) on 2008-03-24 14:14 (Reply)

Thank's for the response. I did upgrade from Beaker-0.5 to Beaker-0.9.1 and now it works. Thank's again for helping me.

#7 Erwin (Homepage) on 2008-03-25 04:16 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	Enclosing asterisks marks text as bold (word), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information? Subscribe to this entry