Thanks for the reply - I've considered the subdomain option but don't want to use it in this case. This article:
http://warpspire.com/posts/url-design/ <http://warpspire.com/posts/url-design/>was previously linked on the forum and summarises very well the reasons I'm keen to go for a URL structure as proposed. On 21 March 2011 22:08, David Warnock <d...@warnock.me.uk> wrote: > Tom, > > >> > An alternative might be to use subdomains eg > > yoursitename.myapp.com > yoursitename.myapp.com/dashboard > yoursitename.myapp.com/users > > I am looking at this for deployment on google app engine (and have not yet > looked at web2py support for it). My understanding is that google app engine > can automatically use the subdomain to restrict the view of the data so that > if I am logged into a.myapp,com I won't be able to access the data for > b.myapp.com > > Sub domains give you nice scaling options in the future such as separate > servers for each domain. > > What I can't help you with (because I am a web2py newbie) is how to make > this work within web2py. > > Hope this helps > > Dave > > -- > Dave Warnock: http://42.blogs.warnock.me.uk > Cycling Blog: http://42bikes.warnock.me.uk > >
