I am lobbying to get Cookie Authentication and a User Properties API into Zope 2.6 for exactly this reason. This would allow you to store/capture user properties, whether preferences, profile, or CRM data as properties of the user. Having it part of acl_users would add additonal extensibility and security, rather than creating new user databases. Standardizing an API will stop the proliferation of conflicting User Products trying to do the same things and "allow the community to move on..." from wasting cycles on redundant infrastructure issues to get to the next level of User Property management and developing more personalization products. This data could be stored in properties with support for vCard import/export. Please add your voice to the mix. Maybe someone else can scream louder than me. Cheers, Trevor
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Shane Landrum Sent: Wednesday, March 20, 2002 9:17 AM To: Eron Lloyd Cc: zope@zope.org Subject: Re: [Zope] Developing a general groupware platform in Zope/Python
On Tue, Mar 19, 2002 at 07:26:12PM -0500, Eron Lloyd (lloyd@lancaster.lib.pa.us) wrote:
I'm building some of the components already, such as vCard/iCalendar python libraries, and the possibilities of using Zope to do groupware stuff is very exciting. The type of platform I envision would enable
Do you have those libraries in public CVS? I know someone was working on Python wrappers for libical a while back, but I don't know how far they got.
srl -- Shane Landrum (srl AT boston DOT com) Software Engineer, boston.com
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )