Results 1 to 3 of 3

Thread: Multi User Database Site, what architecture?

  1. #1
    Join Date
    Oct 2012

    Multi User Database Site, what architecture?

    What architecture should be used?

    Multi users, the users must not be able to see each other's data.

    In the past I done one database and the select statements had the users ID in it, so only the user's data was returned. The user's data is sensitive and users should never be allowed to see each other's data.

    Some sites I've notice have different directories for each user. I am curious why.

    ex: http://mywebsite.com/user1 and http://mywebsite.com/user2

    Are there advantages to this architecture? From a security point of view? Helps prevent cross scripting? How does this work, does each /subdirectory have a separate db table?

    Is there one common code folder?

    I realize these are a lot of questions and the answers are prob way to long.
    Can anyone recommend a site or book that covers this topic?

  2. #2
    Join Date
    Mar 2009
    first of all its up to you how to restrict every user to their own data and how. mostly those site are using same database and tables for all users. the directory or path you see after the actual domain name is not a real directory often, they use URL Rewrite to make it more readable and SEO friendly.

    however you can perform different kinds of validations while working with database.

  3. #3
    Join Date
    Oct 2012
    Hello, maybe you can get some idea from this page (google: ozekisms.com/index.php?owpn=422). When I was coding in PHP the doumentations/examples on this page helped me a lot.


Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
HTML5 Development Center