You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by André Malo <nd...@perlig.de> on 2003/04/30 22:44:59 UTC
Please review the mod_negotiation patch
Folks,
there's a mod_negotiation patch (the "prefer-language" thing) hanging around
in the status file for months. I'm at the stage now, I want to use the
feature provided there for our docs. Just another explanation: I've set up
an example that you may imagine, why the patch would be useful in 2.0, too:
http://httpd.apache.org/docs-2.1/
displays the language, your browser sends via "Accept-Language". Now I'v set
up a somewhat complex set of RewriteRules (in a .htaccess file), that map
virtual directories for every language we provide to the same physical
directory. Try for example
http://httpd.apache.org/docs-2.1/de/
and you'll get the German version, regardless of your browser's preferences.
If you try a document which isn't translated yet (e.g.
<http://httpd.apache.org/docs-2.1/de/bind.html>) you'll get again the one
which matches best your preferences. (I've called that algorithm "forced
negotiation" :-).
However, there are plans for a long time to add some cross-language links
with exactly that feature to the docs. The problem is - if we want to
distribute it with our releases, we cannot force the people to use
mod_rewrite just to *read their docs*. The mod_negotiation patch provides
the key feature, after that we are able to use modules that are still
expected to be available (mod_alias, mod_setenvif and mod_negotiation).
Please consider some words about this topic.
Thanks, nd
--
sub the($){+shift} sub answer (){ord q
[* It is always 42! *] }
print the answer
# André Malo # http://pub.perlig.de/ #
Re: Please review the mod_negotiation patch
Posted by André Malo <nd...@perlig.de>.
* Jeff Trawick wrote:
> André Malo wrote:
>> Folks,
>>
>> there's a mod_negotiation patch (the "prefer-language" thing) hanging around
>> in the status file for months.
>
> +1 (concept)
>
> I'll try hard to find some quiet time and appropriate caffeine delivery
> mechanism in the next day or two.
Thanks!
Installing HTCPCP/1.0 (RFC 2324) may help >:-)
nd
--
my @japh = (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~});
my $japh = q[sub japh { }]; print join #########################
[ $japh =~ /{(.)}/] -> [0] => map $_ -> () # André Malo #
=> @japh; # http://www.perlig.de/ #
Re: Please review the mod_negotiation patch
Posted by Jeff Trawick <tr...@attglobal.net>.
André Malo wrote:
> Folks,
>
> there's a mod_negotiation patch (the "prefer-language" thing) hanging around
> in the status file for months.
+1 (concept)
I'll try hard to find some quiet time and appropriate caffeine delivery
mechanism in the next day or two.
Re: Please review the mod_negotiation patch
Posted by André Malo <nd...@perlig.de>.
* Erik Abele wrote:
> +1 on concept and the patch (mod_negotiation.c r1.110 and r1.115 reviewed
> and tested). As far as I'm allowed to vote ... :-)
Thank you, too :)
Just trying to take advantage of the current reviewing fever and send
another ping: some binding votes available...? [repost follows:]
In the meantime I've committed an accompanying 2.1-config change:
<http://cvs.apache.org/viewcvs.cgi/httpd-2.0/docs/conf/httpd-std.conf.in.diff?r1=1.36&r2=1.37>
Perhaps this helps to explain the desired function better.
-----------------------------------------
there's a mod_negotiation patch (the "prefer-language" thing) hanging around
in the status file for months. I'm at the stage now, I want to use the
feature provided there for our docs. Just another explanation: I've set up
an example that you may imagine, why the patch would be useful in 2.0, too:
http://httpd.apache.org/docs-2.1/
displays the language, your browser sends via "Accept-Language". Now I'v set
up a somewhat complex set of RewriteRules (in a .htaccess file), that map
virtual directories for every language we provide to the same physical
directory. Try for example
http://httpd.apache.org/docs-2.1/de/
and you'll get the German version, regardless of your browser's preferences.
If you try a document which isn't translated yet (e.g.
<http://httpd.apache.org/docs-2.1/de/bind.html>) you'll get again the one
which matches best your preferences. (I've called that algorithm "forced
negotiation" :-).
However, there are plans for a long time to add some cross-language links
with exactly that feature to the docs. The problem is - if we want to
distribute it with our releases, we cannot force the people to use
mod_rewrite just to *read their docs*. The mod_negotiation patch provides
the key feature, after that we are able to use modules that are still
expected to be available (mod_alias, mod_setenvif and mod_negotiation).
Please consider some words about this topic.
Thanks, nd
--
die (eval q-qq:Just Another Perl Hacker
:-)
# André Malo, <http://pub.perlig.de/> #
Re: Please review the mod_negotiation patch
Posted by Erik Abele <er...@codefaktor.de>.
am 12.05.2003 15:54 Uhr schrieb André Malo unter nd@perlig.de:
> * William A. Rowe, Jr. wrote:
>
>> At 06:43 PM 5/6/2003, André Malo wrote:
>>> * André Malo wrote:
>>>
>>>> Folks,
>>>
>>> any considerations on this?
>>
>> Sorry I haven't had time to review the patch in detail; certainly +1
>> on concept though!
>
> Thanks, Will! ;-)
>
> ... any other thoughts? [repost below:]
+1 on concept and the patch (mod_negotiation.c r1.110 and r1.115 reviewed
and tested). As far as I'm allowed to vote ... :-)
BTW, really really great work on the 2.0 docs (chm's, build-sys, etc.) !
Cheers,
Erik
Re: Please review the mod_negotiation patch
Posted by André Malo <nd...@perlig.de>.
* William A. Rowe, Jr. wrote:
> At 06:43 PM 5/6/2003, André Malo wrote:
>>* André Malo wrote:
>>
>>> Folks,
>>
>>any considerations on this?
>
> Sorry I haven't had time to review the patch in detail; certainly +1
> on concept though!
Thanks, Will! ;-)
... any other thoughts? [repost below:]
Side note: In the meantime I've committed an accompanying 2.1-config
change:
<http://cvs.apache.org/viewcvs.cgi/httpd-2.0/docs/conf/httpd-std.conf.in.diff?r1=1.36&r2=1.37>
Perhaps this helps to explain the desired function better.
-----------------------------------------
there's a mod_negotiation patch (the "prefer-language" thing) hanging around
in the status file for months. I'm at the stage now, I want to use the
feature provided there for our docs. Just another explanation: I've set up
an example that you may imagine, why the patch would be useful in 2.0, too:
http://httpd.apache.org/docs-2.1/
displays the language, your browser sends via "Accept-Language". Now I'v set
up a somewhat complex set of RewriteRules (in a .htaccess file), that map
virtual directories for every language we provide to the same physical
directory. Try for example
http://httpd.apache.org/docs-2.1/de/
and you'll get the German version, regardless of your browser's preferences.
If you try a document which isn't translated yet (e.g.
<http://httpd.apache.org/docs-2.1/de/bind.html>) you'll get again the one
which matches best your preferences. (I've called that algorithm "forced
negotiation" :-).
However, there are plans for a long time to add some cross-language links
with exactly that feature to the docs. The problem is - if we want to
distribute it with our releases, we cannot force the people to use
mod_rewrite just to *read their docs*. The mod_negotiation patch provides
the key feature, after that we are able to use modules that are still
expected to be available (mod_alias, mod_setenvif and mod_negotiation).
Please consider some words about this topic.
Thanks, nd
--
package Hacker::Perl::Another::Just;print
qq~@{[reverse split/::/ =>__PACKAGE__]}~;
# André Malo # http://pub.perlig.de #
Re: Please review the mod_negotiation patch
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
At 06:43 PM 5/6/2003, André Malo wrote:
>* André Malo wrote:
>
>> Folks,
>
>any considerations on this?
Sorry I haven't had time to review the patch in detail; certainly +1
on concept though!
>> there's a mod_negotiation patch (the "prefer-language" thing) hanging around
>> in the status file for months. I'm at the stage now, I want to use the
>> feature provided there for our docs. Just another explanation: I've set up
>> an example that you may imagine, why the patch would be useful in 2.0, too:
>>
Re: Please review the mod_negotiation patch
Posted by André Malo <nd...@perlig.de>.
* André Malo wrote:
> Folks,
any considerations on this?
> there's a mod_negotiation patch (the "prefer-language" thing) hanging around
> in the status file for months. I'm at the stage now, I want to use the
> feature provided there for our docs. Just another explanation: I've set up
> an example that you may imagine, why the patch would be useful in 2.0, too:
>
> http://httpd.apache.org/docs-2.1/
>
> displays the language, your browser sends via "Accept-Language". Now I'v set
> up a somewhat complex set of RewriteRules (in a .htaccess file), that map
> virtual directories for every language we provide to the same physical
> directory. Try for example
>
> http://httpd.apache.org/docs-2.1/de/
>
> and you'll get the German version, regardless of your browser's preferences.
> If you try a document which isn't translated yet (e.g.
> <http://httpd.apache.org/docs-2.1/de/bind.html>) you'll get again the one
> which matches best your preferences. (I've called that algorithm "forced
> negotiation" :-).
>
> However, there are plans for a long time to add some cross-language links
> with exactly that feature to the docs. The problem is - if we want to
> distribute it with our releases, we cannot force the people to use
> mod_rewrite just to *read their docs*. The mod_negotiation patch provides
> the key feature, after that we are able to use modules that are still
> expected to be available (mod_alias, mod_setenvif and mod_negotiation).
>
> Please consider some words about this topic.
>
> Thanks, nd
--
>>> Muschelflucht-Zusatzeinrichtung.
>> Shell-Escape ist ja noch klar, aber `Zusatzeinrichtung'?
> extension?
Feature. -- gefunden in de.org.ccc