Well I would go for one application with a little more complex authorization.
We have also different users who are linked to different companies. And offcourse only the data from their company can be viewed. So, at the login I just keep there company-id in a session. (company-id is set in the members table offcourse) If they ask for data you can always see if there is a company-id and only ask for the correct data. Maintaining more applications is difficult. Unless you're sure the application is 100% finished and you don't need to add/change stuff. Maybe you could do it when those organisations have a very large number of members and there are ony a few organisations. Or another reason could be when you think those orginizations have (or will have) other needs. Like organisation A wants an extra field somewhere, organisation B wants another layout... So I hoped I helped you a bit. mguthrie wrote: > > The second solution would need some way to extend Auth to provide checking > the organization ID (possible?). > ----- visit my website at http://www.phpscriptor.com/ http://www.phpscriptor.com/ -- View this message in context: http://www.nabble.com/Design-Question-tp21644511p21645128.html Sent from the Zend Framework mailing list archive at Nabble.com.
