#36 ✓resolved
Russ Smith

Litespeed compatibility

Reported by Russ Smith | March 10th, 2009 @ 08:38 PM | in 1.0

It really seems like the LSAPI doesn't act like it's supposed to but with this small change, it looks like everything plays nicely.

Comments and changes to this ticket

  • Russ Smith

    Russ Smith March 11th, 2009 @ 03:47 AM

    One more update. This make the lsapi act properly by passing it's behavior over to StringIO.

  • josh

    josh March 11th, 2009 @ 02:22 PM

    • Milestone set to 1.0

    Can you please add some tests to help document the extra to_s. And shouldn't we need this extra to_s on every input read?

  • Russ Smith

    Russ Smith March 11th, 2009 @ 03:49 PM

    Actually, the second diff makes the LSAPI work correctly by passing itself off to StringIO. I can look into tests for it, but I think by the tests not failing by adding this change show that it works correctly.

    If my C was better I would modify the ruby-lsapi gem instead to make it work properly.

  • josh

    josh March 11th, 2009 @ 05:09 PM

    • Assigned user set to “josh”
    • State changed from “new” to “open”

    Gotcha, should I just go head and apply the second patch only? This fixes the issues you had with Rails as well, correct?

  • Russ Smith

    Russ Smith March 11th, 2009 @ 05:21 PM

    Yes it does. Sorry for the confusion. It took me a while to track down where the error were originating from.

  • josh

    josh March 11th, 2009 @ 05:48 PM

    • State changed from “open” to “resolved”

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

People watching this ticket