[patch] RSTRING fixes for 1.9

Server Mongrel
1

doing what ebb did. change RSTRING(str)->ptr and RSTRING(str)->len to
RSTRING_PTR(str) and RSTRING_LEN(str) and define a backwards-compatible
macro…

i dont think i had to fix this before. maybe thin or something already
had installed a working http11.so

maybe the mongrel parser should be its own package, since so much stuff
uses it w/o the rest of mongrel?

side note. mongrel.rubyforge trac doesnt use the same accts as toplevel
rubyforge? (why im mailing this)

best,
C

2

On Thu, Apr 17, 2008 at 12:21 PM, cdr [email protected] wrote:

doing what ebb did. change RSTRING(str)->ptr and RSTRING(str)->len to RSTRING_PTR(str) and RSTRING_LEN(str) and define a backwards-compatible macro…

i dont think i had to fix this before. maybe thin or something already had installed a working http11.so

This is already fixed in Mongrel

http://mongrel.rubyforge.org/changeset/895

maybe the mongrel parser should be its own package, since so much stuff uses it w/o the rest of mongrel?

Mongrel HTTP parser is core of mongrel, it shouldn’t be splitted.

side note. mongrel.rubyforge trac doesnt use the same accts as toplevel rubyforge? (why im mailing this)

No, RubyForge do not offer Trac functionality, after all RubyForge is
GForge / SourceForge software (PHP) and not Python.

Mongrel Trac is not hosted at rubyforge, even so, trac and GForge
software cannot share authorization information (well, not without
tweaking).

–
Luis L.
Multimedia systems

Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams