IMHO commit and let it be fixed in trunk.
-Original Message-
From: Jim Jagielski [mailto:j...@jagunet.com]
Sent: Freitag, 26. August 2011 16:34
To: dev@httpd.apache.org
Subject: PoC ready
Should I commit or post?
-Original Message-
From: Plüm, Rüdiger, VF-Group [mailto:ruediger.pl...@vodafone.com]
Sent: Freitag, 26. August 2011 16:38
To: dev@httpd.apache.org
Subject: RE: PoC ready
IMHO commit and let it be fixed in trunk.
I mean improved :-).
Not to imply your code has errors
On Aug 26, 2011, at 10:40 AM, Plüm, Rüdiger, VF-Group wrote:
-Original Message-
From: Plüm, Rüdiger, VF-Group [mailto:ruediger.pl...@vodafone.com]
Sent: Freitag, 26. August 2011 16:38
To: dev@httpd.apache.org
Subject: RE: PoC ready
IMHO commit and let it be fixed in trunk
Committed… r 1162131
To: dev@httpd.apache.org
Subject: Re: PoC ready
Committed... r 1162131
: Freitag, 26. August 2011 17:19
To: dev@httpd.apache.org
Subject: Re: PoC ready
Committed... r 1162131
;
num_ranges++;
-range++;
+}
Otherwise I think 0-1,1000-1001
will result in
0-1
Regards
Rüdiger
-Original Message-
From: Jim Jagielski [mailto:j...@jagunet.com]
Sent: Freitag, 26. August 2011 17:19
To: dev@httpd.apache.org
Subject: Re: PoC
As a quick ref, here's the qd ruby script I'm using
for the merging algo:
aa = [1-1, 100-200, 1000-2000, 950-1050, 980-3000, 50-70, 5000-6000, 6001-7000, 4000-6000, 10-4000]
aa = [5000-6000, 6001-7000]
in_merge = false
ostart = 0
oend = 0
num_ranges = 0
ret =
overlaps = 0
reversals = 0
aa.each
