Re: how to encrypt the password/login for the blog.rb example?
2008/2/25, Albert Ng [EMAIL PROTECTED]: I'll keep that in mind. As an aside, using this gem, how would I go about changing the user without closing the browser or raising «Unauthorized»? That last pops up a log-in window that can't authorize (have to press escape). There is no perfect solution. Here is what I use in jQuery : // idea from : http://nanodocumet.homedns.org/rest/ $('#header A.disconnect').click(function() { try { if ($.browser.msie) { // IE clear HTTP Authentication document.execCommand(ClearAuthenticationCache); } else { var xhr = new XMLHttpRequest(); xhr.open(GET, /logout, true, logout, logout); xhr.send(null); xhr.abort(); } } catch(e) { error(e) } }) - * the /logout url should respond Unauthorized for the logout:logout credential * the xhr.open is called with async to true, otherwise the browser shows the login window -- Cheers, Jonas ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Are we ready for a release ?
Hi campers, what do you think of releasing the current trunk as camping-1.6 ? Nothing much has moved since a while and apart from FastCGI, I believe most bugs where ironed out. After the gem release, I propose putting some effort on documentation and how to use Rack's FastCGI. When that's done, we'll have a Rubyforge announcement and such. /me is waiting for community input -- Cheers, Jonas ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Are we ready for a release ?
Hello all, On Wed, Mar 12, 2008 at 05:58:00PM +0100, Jonas Pfenniger wrote: what do you think of releasing the current trunk as camping-1.6 ? Nothing much has moved since a while and apart from FastCGI, I believe most bugs where ironed out. Yeah, I see in the roadmap that there are two bugs open (you mention one here). Are these real blockers? It would be greate to have a relase. After the gem release, I propose putting some effort on documentation and how to use Rack's FastCGI. When that's done, we'll have a Rubyforge announcement and such. Don't forget the tarball release. ;) By the way, do you/we have any release notes, or NEWS listing the new features? Paul -- PhD Student @ Eindhoven | email: [EMAIL PROTECTED] University of Technology, The Netherlands | JID: [EMAIL PROTECTED] Using the Power of Debian GNU/Linux | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Are we ready for a release ?
2008/3/12, Paul van Tilburg [EMAIL PROTECTED]: Hello all, On Wed, Mar 12, 2008 at 05:58:00PM +0100, Jonas Pfenniger wrote: what do you think of releasing the current trunk as camping-1.6 ? Nothing much has moved since a while and apart from FastCGI, I believe most bugs where ironed out. Yeah, I see in the roadmap that there are two bugs open (you mention one here). Are these real blockers? It would be greate to have a relase. You're right. Actually the ESPIPE error (#130) is hard to solve. jsheets proposed to read the full upload in a StringIO. That idea clearly doesn't scale to big files. The ideal solution would be to rewrite that big chunk in #initialize to not use IO#revert but I never had the guts to do it. So while I could wait for somebody to do the work, I prefer to state that file uploads doesn't work in CGI instead of penalizing the other adapters. I clearly have to be documented somewhere at least. After the gem release, I propose putting some effort on documentation and how to use Rack's FastCGI. When that's done, we'll have a Rubyforge announcement and such. Don't forget the tarball release. ;) Noted By the way, do you/we have any release notes, or NEWS listing the new features? The changes are only noted in the SVN actually. I'll scan trough it when updating the doc. -- Cheers, Jonas ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list