Re: New module - (session/authentication) seeking a name

2004-05-13 Thread David Nicol
mine is
AIS::client
which I can rename to match the others if you come up
with a good name.
I have not tested AIS::client with mp and presume it is
broken there.  Turning www::authen::simple into an AIS
client would allow you to centralize your authentication.


--
[EMAIL PROTECTED]
I know you, junk mail. Gonna miss you when you're gone


Re: Duplicated modules

2004-05-13 Thread IvorW
- Original Message - 
From: Jose Alves de Castro [EMAIL PROTECTED]
To: IvorW [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: 13 May 2004 11:23
Subject: Re: Duplicated modules


 
  Having said that, are we just reinventing Perlmonks?
 
 That, I do not know... :-|

Ah, you do not know of the monastery. Check out http://perlmonks.org, 
which is a thriving on-line community and discussion forum, which is
completely searchable.

Perlmonks is not everybody's cup of tea (sorry, please excuse the UK idiom),
but everyone must admit that the site has an extensive linked set of
documentation, which includes numerous tutorials and FAQs which can be
used as reference, even when not actively participating in the site.


Re: Duplicated modules

2004-05-13 Thread Randy W. Sims
On 5/13/2004 7:19 PM, IvorW wrote:

- Original Message - 
From: Jose Alves de Castro [EMAIL PROTECTED]
To: IvorW [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: 13 May 2004 11:23
Subject: Re: Duplicated modules



Having said that, are we just reinventing Perlmonks?
That, I do not know... :-|


Ah, you do not know of the monastery. Check out http://perlmonks.org, 
which is a thriving on-line community and discussion forum, which is
completely searchable.

Perlmonks is not everybody's cup of tea (sorry, please excuse the UK idiom),
but everyone must admit that the site has an extensive linked set of
documentation, which includes numerous tutorials and FAQs which can be
used as reference, even when not actively participating in the site.
It would be much nicer if it was readable as a nntp or at least a 
mailing list; I've always found http-based discussion boardss awkward to 
navigate and difficult to figure out what I have and haven't read. 
Wonder why this hasn't been done?

Randy.




Re: Duplicated modules

2004-05-13 Thread Mark Stosberg
On Thu, May 13, 2004 at 07:38:51PM -0400, Randy W. Sims wrote:
 
 It would be much nicer if [perlmonks] was readable as a nntp or at least a 
 mailing list; I've always found http-based discussion boardss awkward to 
 navigate and difficult to figure out what I have and haven't read. 
 Wonder why this hasn't been done?

There is an RSS feed:
http://www.perlmonks.org/headlines.rdf

RSS readers often help you manage what you have and haven't read. I like
to use 'snownews' in a terminal.

Also, you can the voting feature to help keep track of what yo've read.
Just vote everything you read up or down. :) Admittedly, that strategy
works best once you've been there a while and have lots of votes to use.

Mark

-- 
http://mark.stosberg.com/ 


Re: New module - (session/authentication) seeking a name

2004-05-13 Thread jmiller
On Wed, 12 May 2004, David Nicol wrote:

 mine is
 AIS::client
 which I can rename to match the others if you come up
 with a good name.

 I have not tested AIS::client with mp and presume it is
 broken there.  Turning www::authen::simple into an AIS
 client would allow you to centralize your authentication.


I hadn't heard of AIS before. Sounds like it would make a nice additional
authentication method. Part of my TODO is to abstract both the
authentication and storage methods. I should be able to add this auth
method after that (though, it doesn't offer any group based permissions,
so that would still need handled locally).

I looked over AIS::client... there are a lot of exit statements in there,
and a lot of hardcoded HTML. It'd be nice if allowed the user of the
module to handle those parts, and just supplied the information it would
need (the full URL of the AIS server when needed, etc), just a thought.
And if it returned some failure condition, it wouldn't have to exit(), and
could allow the client to handle those errors.

It might be a while before I get the authentication and storage methods
abstracted (shouldn't be all that difficult, but it's not on the top of my
TODO list right now). When I do, I'll definately look into AIS, and see if
I can find similar resources out there.

Thanks for the info, I don't think I would have found that without your
link.
--
Josh I.