From: Trans <transfire@...>
Date: 2007-02-06T07:47:41+09:00
Subject: Re: Contributing back to the source (Was: Gem Namespaces)



On Feb 5, 2:15 pm, ara.t.how...@noaa.gov wrote:
> On Tue, 6 Feb 2007, Eric Hodel wrote:
>
> > Ryan implemented an auto-config, but still as a separate stage...  It would
> > have been nice to know about your patch before we did it.  I'd still take a
> > look.
>
> i'm with eric.  when you take a wrong turn on the trail turn back fast!  not
> that i'm saying YOU took a wrong turn, but we've forked and, the longer we
> continue, the harder it will be.  rubyforge cannot possibly by important
> enough as a script to require a forked project right?

fair enough. I'll send you a copy of mine and see waht we can work
out.

> >> Aside, I sort of wish it didn't use HTTPAccess2, it seems quite a hefty lib
> >> for what rubyforge.rb is using it for. But I'm not sure, maybe there's no
> >> better option.
>
> > HTTPAccess2 has sessions stuff built-in.  *shrug*.
>
> i initiallly used http-access2 for 4 reasons
>
>    - proxy support
>
>    - debug support.  i had to use this heavily as http-access2 itself had
>      several bugs i worked in runtime patches for
>
>    - cookie support
>
>    - redirection support
>
> these were all things i had no interest in maintaining myself.

those are all good reasons.

> it would easy to replace http-access2 with something else if you have a
> suggestion?

i don't know of any.

t.