derek keller said:
> granted, i am probably missing the picture of what you need. if you
> have an existing set of permissions and url rewrites on your apache
> installation in a big bunch of scattered htaccess files, it wouldn't be
> hard to translate those into aolserver's url registeration and
i didn't mean any personal criticism.
what i do mean is that it's not easy to move between systems,
especially when you don't have the time or money to spend doing it.
in these situations, if docs existed it might make the transition
easier as there probably are elements of apache functionality t
?
Regards.
Jean-Fabrice RABAUTE
Core Services - Enjoy the future today
http://www.core-services.fr
Mob: +33 (0)6 13 82 67 67
-Message d'origine-
De : AOLserver Discussion [mailto:[EMAIL PROTECTED] la part
de tammy
Envoye : vendredi 1 aout 2003 20:51
A : [EMAIL PROTECTED]
Objet : Re: [AO
This seems really close to what .vuh files do in OpenACS... unless I'm
mistaken. Maybe a simple/quick fix is to write a quick script to just
parse all the .htaccess rewrite commands into simple .vuh files? Or is
there more to this I'm missing? Probably so huh?!
t
On Friday, August 1, 2003,
Peter M. Jansson said:
>> the problem isn't
>> that the functionality is missing, its not knowning syntax.
>
> Patrick's case is that he wants to use a 3rd-party package that requires
> Apache semantics, and it's not a matter of his knowing the syntax,
> (which he probably does anyway), but it's th
derek keller said:
> apache compatibility in aolserver? band-aid.
But if it keeps blood from spurting, a band-aid can indeed be a useful thing.
> make some docs for apache users: "how to do apache-specific tasks in
> aolserver" with some examples. the problem isn't that the
> functionality is
> the problem isn't
> that the functionality is missing, its not knowning syntax.
Patrick's case is that he wants to use a 3rd-party package that requires
Apache semantics, and it's not a matter of his knowing the syntax,
(which he probably does anyway), but it's that the 3rd-party packages do
aut
I really like this idea. Compiling a how to do this apache thing using
AOLserver tools would go a long way. AOLserver users would see what cool
things Apache can do, and we can learn areas where AOLserver can't do
what Apache can do. From there we would need to decide if we want
AOLserver to do tho
apache compatibility in aolserver? band-aid.
keep the products separate but functionally similar, which they are.
make some docs for apache users: "how to do apache-specific tasks in
aolserver" with some examples. the problem isn't that the
functionality is missing, its not knowning syntax.
i
