And I believe that is the point : Our own components means our own methods and that makes it harder to use each-others stuff. Whether we use Zope-stype Interfaces or just plain Python classes isn't the problem : The problem is agreeing on a single set of methods that all implementations of a component adhere to.
- Ian Sparks.
I agree.
I would like to start W/ UserKit. I like the properties and methods in UserKit
Except that my user classes are just data objects, they cannot login or out. You need a UserManager class for that.
What do you all think?
For historical reasons I would recommend starting with a user management system, but I would like to propse another set of interfaces for:
1) User class
A class that a servlet will use at runtime with
Should have:
user.name
user.userID
xxxxx
2) UserManager class
A class that can login / logout a user
Can also retrieve Userinformaion from the datastore and update it.-Aaron
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
