Some ideas to do with permissions and extending torque ... I think many applications will have the requirement for administering users/roles/permissions and that this will work best if built in to torque as well. Common permissions should also be automatically created. Example: For Customer object with fields NAME, COMPANY, EMAIL, PHONE the CustomerPeer class generated by torque should have access checks such as CanInsert, CanUpdate, CanDelete, CanSelect that guard functions such as doSelect in such a manner that the current user would have to be assigned a CanInsert permission or be assigned a role that has CanInsert priveleges With this approach and an admin app built into newapp (and hopefully into every other app :-)) turbine applications can have a relatively high level of security, out of the box, and by design, leaving developers free to approach things that don't involve re-inventing the wheel. I've also contributed an example peer app to jvz and hope to soon see it in CVS where I can keep it synchronized. If development of the admin app has started yet, I would also like to help since that is an area I'm working on now for the contributed example application. __________________________________________________ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/ ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
