search for: lsapi

Hi, If you have been using or evaluating LiteSpeed web server + Ruby LSAPI setup for Rails application, please make sure your are using the latest release, Ruby LSAPI 1.9 and LSWS 2.2.2. We have been fixing a few bugs that causes DB connection errors, incompatibilities with WEBrick/Mongrel and ruby process management issues, currently, all bug reported has been addressed...

Hi, First, my thanks to Zed for including LiteSpeed in cgi.rb vulnerability report. Appreciated! I just got time to review ruby-lsapi code and test the vulnerability against LiteSpeed. I found that, in our latest ruby-lsapi release 1.11, lsapi_read() function returns Qnil when the end of request body has been reached. So, in theory, LiteSpeed should not be vulnerable to this attack. Our test results confirmed what I expected, 500...

Hi, I am glad to announce that Ruby LSAPI extension 1.4 is released, in this release we mainly addressed two issues, one is that a worker process does not remain persistent if a request has been canceled in the middle, this is addressed in 1.4. Another one is that process manager may create a lot more worker processes than the value config...

Hi, We released Ruby LSAPI 1.6 today to address a issue that some ruby processes can only be terminated with SIGKILL (-9). This is due to conflicts in signal handler between LSAPI and ruby. Upgrade is highly recommended for existing user of Ruby LSAPI + LiteSpeed. Best Regards, -- George Wang http://www.litespeedtech.com -...

Apologies in advance if this ignites a war of comflicting opinions.... I''m a few days away from going live with my first RoR application. It is completely database centric and each user will have his own queries so cacheing will not really help. I have a dedicated linux server being built by my hosting provider and I need to tell them which webserver to use. The databse is MySQL

Hi, We released Ruby LSAPI extension 1.5 to address a bug introduced in 1.4 that may cause small post requests blocking. If you are using LiteSpeed + Ruby LSAPI, please upgrade. Best Regards, -- George Wang LiteSpeed Web Server http://www.litespeedtech.com/

...ys at Rails framework startup, usually, fixed number of Rails applications need to be started at server startup time, no matter how high or how low the traffic volumes are. It is not flexible and number of Rails applications can be hosted on one server is severely limited by it memory size. Rails + LSAPI minimizes the startup cost of Rails framework and make dynamic spawning less problematic, number of Rails instances needed can be dynamically adjusted by web server based on traffic volume. System resource will be used more efficiently and hosting more Rails applications on one server becomes possi...

...so maybe it has to do with that (no restarts during the night, a memory leak somewhere?). It started with Mongrel 1.0.1 but .... just a few days before I upgraded to Mongrel 1.0.1, I upgraded to Rails 1.2. So I''m not sure who''s the culprit. A few days ago I switched to the lsapi RailsRunner and the problem has disappeared, so Mongrel definitely is involved. Just thought I''d give it a mention. Ant btw Zed: the .nl welcomes you, the land of cheese and clogs. Actually it''s nice here, you should visit us someday! Joost.

...er setup people have had good luck with. I''m looking for something that is: 1. Stable 2. Easy to setup 3. Secure (sorry but Windows is ruled out here) My deployment will either be on Fedora Core 5 or possible Mac OS X Server. Currently I''ve been looking at Litespeed and their LSAPI integration and am tempted by that. I also have looked at Mongrel with Pound/Pens/Balance. I *could* do Apache 2.2 and Mongrel but want to avoid Apache if possible as I''d like to keep my memory contraints as low as possible and I''ve found Apache can be a bit of a memory hog...

...Rails APIs and stuff is not as good as I''m use to in Perl (particulariy CPAN). No being critical, just saying the Rails documentation left me hanging more than once and guessing as to what I was doing wrong. Production deployment is a bit much. I''ve found using Litespeed and LSAPI was the easiest to get to production than the Apache + mod_proxy + mongrel cluster solution. Using Turbogears (Python) Pretty productive here as well right off the bat. Documentation is sparse at best and this hampers you when you want to step out of the box. Production is pretty easy, using...

...in the enterprise I''ve done a lot of testing with both Ruby and with Rails. First, I haven''t hit any issues where I''ve found it too slow. On the contrary I''ve found that when you get Rails setup correctly it performs exceptionally well (Litespeed''s LSAPI is insanely fast once configured). It certainly scales. The websites are out there proving this (Basecamp, 43Things, Yakima Herald, etc.) Sure, these sites aren''t eBay or Amazon but toss enough hardware at Rails and it could be eBay. I take script VERY seriously. Occasionally I'...

Hi, We have developed a small RoR app that runs fine on a standard IBM thinkpad (1GB mem) but runsmuch slower when on an IBM x460 Redhat machine (32GB ram). The x460 server has hardly any thing running on it at present, so that not the issue. We are busy checking the config and permissions of the user account used to run the app., but I was wondering if you guys have heard anything about redhat

Yo Zed, Just curious -- what do you think of the LiteSpeed server? Is it better than Lighty? Does it (gasp!) also serve Rails apps like Mongrel? I think I read that LiteSpeed doesn''t have proxying support. Thanks, Joe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Performace hits? Integration with existing applications? Security? Bugs? Memory use? -Ben Lisbakken -- Posted via http://www.ruby-forum.com/.