--0016361e815cc269a80499bf93cd
Content-Type: text/plain; charset=ISO-8859-1

I've written a mod_perl application, "mod_auth_any", that allows users to be
authenticated by any authentication mechanism or provider. It currently
supports Shibboleth, OpenID (Google), LDAP, and basic auth. Are there
published guidelines on how to package modules that are based on mod_perl?
The modules.apache.org site lists over 500 modules. Are any of these written
in mod_perl?

Kim

--0016361e815cc269a80499bf93cd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I've written a mod_perl application, "mod_auth_any", that all=
ows users to be authenticated by any authentication mechanism or provider. =
It currently supports Shibboleth, OpenID (Google), LDAP, and basic auth. Ar=
e there published guidelines on how to package modules that are based on mo=
d_perl? The <a href=3D"http://modules.apache.org">modules.apache.org</a> si=
te lists over 500 modules. Are any of these written in mod_perl?<br>
<br>Kim<br>

--0016361e815cc269a80499bf93cd--

Hi Kim,

> Are there
> published guidelines on how to package modules that are based on mod_perl?

Yes, they are released on CPAN.
http://perl.apache.org/docs/general/cpan_mod_dev/cpan_mod_de v.html

> The modules.apache.org site lists over 500 modules. Are any of these written
> in mod_perl?

No, that directory is for C modules. The mod_perl ones are all on CPAN.

- Perrin

--0016361e815c4c9a750499d39ab2
Content-Type: text/plain; charset=ISO-8859-1

Thanks Perrin. Would it be appropriate to name and package our application
as "Apache::AuthAny" or "Apache2::AuthAny". I have not tested under Apache
1.3, and have no intent to do so.

Kim

On Fri, Jan 14, 2011 at 8:33 AM, Perrin Harkins <perrin [at] elem.com> wrote:

> Hi Kim,
>
> > Are there
> > published guidelines on how to package modules that are based on
> mod_perl?
>
> Yes, they are released on CPAN.
> http://perl.apache.org/docs/general/cpan_mod_dev/cpan_mod_de v.html
>
> > The modules.apache.org site lists over 500 modules. Are any of these
> written
> > in mod_perl?
>
> No, that directory is for C modules. The mod_perl ones are all on CPAN.
>
> - Perrin
>

--0016361e815c4c9a750499d39ab2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks Perrin. Would it be appropriate to name and package our application =
as "Apache::AuthAny" or "Apache2::AuthAny". I have not =
tested under Apache 1.3, and have no intent to do so.<br><br>Kim<br><br>
<div class=3D"gmail_quote">On Fri, Jan 14, 2011 at 8:33 AM, Perrin Harkins =
<span dir=3D"ltr"><<a href=3D"mailto:perrin [at] elem.com">perrin [at] elem.com</a=
>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin: 0=
pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: =
1ex;">
Hi Kim,<br>
<div class=3D"im"><br>
> Are there<br>
> published guidelines on how to package modules that are based on mod_p=
erl?<br>
<br>
</div>Yes, they are released on CPAN.<br>
<a href=3D"http://perl.apache.org/docs/general/cpan_mod_dev/cpan_mod_dev.ht=
ml" target=3D"_blank">http://perl.apache.org/docs/general/cpan_m od_dev/cpan=
_mod_dev.html</a><br>
<div class=3D"im"><br>
> The <a href=3D"http://modules.apache.org" target=3D"_blank">modules.ap=
ache.org</a> site lists over 500 modules. Are any of these written<br>
> in mod_perl?<br>
<br>
</div>No, that directory is for C modules. =A0The mod_perl ones are all on =
CPAN.<br>
<font color=3D"#888888"><br>
- Perrin<br>
</font></blockquote></div><br>

--0016361e815c4c9a750499d39ab2--

On Fri, Jan 14, 2011 at 2:40 PM, Kim Goldov <kgoldov [at] gmail.com> wrote:
> Thanks Perrin. Would it be appropriate to name and package our application
> as "Apache::AuthAny" or "Apache2::AuthAny". I have not tested under Apache
> 1.3, and have no intent to do so.

I'd go with Apache2::AuthAny then.

- Perrin