web service single-sign-on identity module(s)
I have revised the AIS client module and the new version is driving the signin of the tool at http://tipjar.com/rcgi/featurematrix/matrix (the new code is more robust than the old, which would do endless loops if you didn't have cookies on.) my question for module authors list is, what is a good interface for letting the identity out? Here is what I'm going with at the current time: use AISclient (optional parameters); you put that line near the beginning of your one-off CGI and it either exits or you get a valid e-mail address imported into your package in a variable called $AIS_IDENTITY and a persistent stash for any use called %AIS_STASH I would like to hear from people who use idenity and session modules in web services about what interfaces they like, if there is a de-facto standard interface that it would be good to mimick. Another issue is how much data about the identities to collect and distribute with each sign-in. Things like firstname initial lastname grooviness rating current available buying power and so on. I set up a mailing list for discussion of the project at http://mail.nongnu.org/mailman/listinfo/tjais-dev David Nicol -- david nicol The elves have left the building
Re: RFC: Date::Iterator
On Friday, December 19, 2003, at 12:19 PM, Marco Marongiu wrote: Could I contribute to the DateTime project? I think I can't. Working with calendars and times would require me an effort bigger than I can take. A contribution you could make fairly easily is a documentation patch, showing how it could be used for the specific case you needed in your work. Proliferation of modules on CPAN is evil? Maybe. Maybe not. It could create confusion, you are right. But... well, I'll say in italian: "Cio` che hai in piu` non ti impoverisce"; I don't have a good translation in english, but it could sound like "things you got and don't need don't make you poor". It's a natural selection process: people search for modules that do the job, read the docs and make a choice. If my module is bad, they simply won't use it. Yeah, but it still stays on CPAN to confuse the next person. Natural selection isn't quite the right metaphor here, since modules don't die out from disuse. -Ken
Re: Date::Iterator, pollution, rating system, and how to make CPAN a better place [was: Re: RFC: Date::Iterator]
* Lincoln A. Baxter <[EMAIL PROTECTED]> [2003-12-24 09:39]: > I think it _is_ useful to get the word 'Day' in there, since > someone _could_ come along and choose to implement > Date::Calc::Hour::Iterator... (or HourIterator) .. (you would > be setting the pattern I would think) etc. If it were just > ::Iterator that would be precluded. If you're gonna go that route and put Day in the name but as a separate namespace level, it should be Date::Calc::Iterator::Day so there isn't a new 3rd level namespace for every date iterator module with only one 4th level name in it. -- Regards, Aristotle "If you can't laugh at yourself, you don't take life seriously enough."
Re: Licenses for Perl Distributions As Displayed on search.cpan.org
On Tue, Dec 23, 2003 at 08:35:09PM -0500, Randy W. Sims wrote: > The latest snapshot of MakeMaker does have support for a LICENSE > parameter in your Makefile.PL. I received a patch for it but haven't applied it yet. -- Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/ I stare into the Abyss, and it avoids making eye contact.
