[Zope3-dev] IsarSprint topics - Zope 3 application components

Stephan Richter srichter at cosmos.phy.tufts.edu
Wed Sep 8 08:42:48 EDT 2004


Here my comments just for the records.

On Wednesday 08 September 2004 02:47, Helmut Merz wrote:
> - Principal sources, esp. LDAP

Note that Roger and others have already worked on a LDAP source. You 
definitely want to coordinate with them. I think a SQL- or /etc/passwd-based 
source would also be really cool. You can use the corresponding chapter in 
the Zope 3 book as a start.

> - WebDAV

I think this is really, really important. Not having COPY, MOVE and all the 
locking stuff, makes the current WebDAV support quiet unusable.

> - CookieAuthentication

I think this one is really important, if we want to develop real Web sites. I 
would suggest trying to come up with a generic mechanism that determines the 
username/password pair (via an adapter), so that other authentication 
methods, such as URL-encoded authentication can also be easily done.

> - Sessions

We currently have already some session support, but Jim was not happy with it. 
You should look into the proposals whether any deals with sessions and query 
Jim about the deficiencies of the current implementation.

> - Reference Engine (this is my personal favorite here)

This has been discussed numerous times and many proposals have been written. 
Before you start to work on this one, please read

http://dev.zope.org/Zope3/AssociationService
http://dev.zope.org/Zope3/RelationshipService
http://dev.zope.org/Zope3/RelationManager

The first one is the latest. Before you tackle such a beast, I would really 
like to see a proposal. (You have 4 weeks, which is plenty of time.)

> - SOAP

I would personally not attack this one, since it is a lot of work and not very 
rewarding, if you do not have any specific application in mind.

> - User/member management

Yes, I think this would be a great sprint task. All the underlying 
technologies are in place.

> - Search forms

What's that? I think before you can build high-level search forms, you need to 
make sure the indexing and simple querying is working correctly. Jim has 
pointed out many issues left to do. I think finishing the index to-do list 
would be a better problem to attack.

> - Mailing list manager

I really hope you do this by integrating Mailman. Playing nice with other 
Python projects is harder, but more efficient in the long run. Let Barry and 
other Mailman developers worry about the hard issues concerning mailing 
lists. I once tried to interface Mailman with Zope 2 (ZMailman) and got quiet 
far.

> - Web CMS - hopefully we get some input from the
>   CastleSprint2 about this topic 
> (http://plone.org/events/conferences/2/CastleSprint2)
> - My personal project: LOOPS (Linked Objects for
>   Organizational Process Services), a task (project, issue,
>   ...) and resource management framework
> - Also from my work: A learning management system
> - PetStore or some other kind of "blueprint application"
>   e.g. for marketing purposes or as a starting point for
>   development

Honestly, I think all of these are too ambitious for a sprint. 

Regards,
Stephan
-- 
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training


More information about the Zope3-dev mailing list