Re: [PHP] Web application architecture (subdomain vs. sub directory)
Tim Martens wrote: Thanks for all your answers. To clarify my question, I'm looking for advice regarding how best to set up users for a web app, e.g., username.myapp.com vs myapp.com/username and the pros and cons of each. Using username.myapp.com means defining that name in your DNS and having a separate virtual host definition in your apache config. Using myapp.com/username means having one virtual host, and no extra DNS records. One is not necessarily better or worse than the other - to me it's mostly about presentation and I would go for the myapp.com/username option. This (in my mind) puts username a level lower than myapp, whereas username.myapp.com does the opposite. -- Per Jessen, Zürich (17.7°C) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
Shreyas Agasthya wrote: I am not sure who the end-users are for your website but if you are concerned about scalability, I would definitely go for a sub-domain approach. Assuming you approach a CDN like Akamai and you want to offload the traffic to come from the cloud, it's lot easier for you to integrate with them and to maintain. The subdirectory approach, whereas, is very cumbersome and takes more work at your end to paraphrase the whole set-up should the needs change going forward. The subdirectory approach is easily rewritten to an internal subdomain structure. -- Per Jessen, Zürich (17.7°C) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On 26 August 2010 08:08, Per Jessen p...@computer.org wrote: Tim Martens wrote: Thanks for all your answers. To clarify my question, I'm looking for advice regarding how best to set up users for a web app, e.g., username.myapp.com vs myapp.com/username and the pros and cons of each. Using username.myapp.com means defining that name in your DNS and having a separate virtual host definition in your apache config. While offtopic and nothing to do with PHP I think this should be corrected: you can set a *.yourdomain rule which matches all subdomains not explicitly set. So no, you do not need to define every single name as a DNS record. Regards Peter -- hype WWW: http://plphp.dk / http://plind.dk LinkedIn: http://www.linkedin.com/in/plind BeWelcome/Couchsurfing: Fake51 Twitter: http://twitter.com/kafe15 /hype -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
Peter Lind wrote: On 26 August 2010 08:08, Per Jessen p...@computer.org wrote: Tim Martens wrote: Thanks for all your answers. To clarify my question, I'm looking for advice regarding how best to set up users for a web app, e.g., username.myapp.com vs myapp.com/username and the pros and cons of each. Using username.myapp.com means defining that name in your DNS and having a separate virtual host definition in your apache config. While offtopic and nothing to do with PHP I think this should be corrected: you can set a *.yourdomain rule which matches all subdomains not explicitly set. So no, you do not need to define every single name as a DNS record. Good point. Not sure I would personally want to use wildcards, but it's perfectly valid. -- Per Jessen, Zürich (17.7°C) -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
At 1:45 PM -0500 8/25/10, Tim Martens wrote: Hi Everyone, New to the list. Hello! I'm in the customer discovery phase for a Health IT web application concept I have. My programmer is new to web apps, but not to programming and is set up with LAM(PHP). We're still debating weather to use a framework or to go with Rasmus's no framework framework approach. Language/Framework decisions aside... my main question is about subdomain ( customerx.appname.com vs subdirectory (appname.com/customerx/) models for instances of individual customers' accounts. It seems most people are opting for the former -- is this but a trebd? -- but I see flickr use the latter. The guys at Particletree (i.e., Wufoo) wrote a blog post about it ( http://particletree.com/notebook/subdomains-development-sucks/) years ago to which they still attest. They say the subdirectory model is much easier and faster to develop and deploy. We are developing locally on our macs and will be using Mecurial/Bitbucket for CVS. I'm really lost on this issue as all my searches turn up stuff on SEO/SEM. Is one approach easier that the other? What about security and scalability considerations? I would very much appreciate your opinions as to the pros and cons of each approach. As an aside, does anyone have some advice about rapid PHP deployment, i.e., pushing new features to production daily in micro iterations vs the typical milestone approach? Are there any good tools for this? What about hosts? Thanks all, Tim Tim: My recommendations: 1. No framework. Learn one thing, namely what you want to do and not two (i.e., what you want to do and a framework). I did not know that Rasmus said that, but I listen to what he says. 2. Use directories. They are much simpler to use and easy to create/change/delete/scale/make-secure. -- SEO stuff does not apply here. 3. Investigate Agile development. 4. Host? Roll the dice like the rest of us. Cheers, tedd -- --- http://sperling.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
At 4:45 PM -0500 8/25/10, Tim Martens wrote: Thanks for all your answers. To clarify my question, I'm looking for advice regarding how best to set up users for a web app, e.g., username.myapp.comvs myapp.com/username and the pros and cons of each. All users will be using essentially the same app that will have their data in their account. I can see the logic of setting up subdomain for things like a universal login and, say, metrics for example. Is javascripting more difficult across subdomains? Is one approach beter in terms of security? Essentially the entire app will be running on https. Thanks again! Tim Tim: That's a different question -- you should post another question rather than continue the old thread regarding something else. Cheers, tedd -- --- http://sperling.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Web application architecture (subdomain vs. sub directory)
From: tedd At 1:45 PM -0500 8/25/10, Tim Martens wrote: Hi Everyone, New to the list. Hello! I'm in the customer discovery phase for a Health IT web application concept I have. My programmer is new to web apps, but not to programming and is set up with LAM(PHP). We're still debating weather to use a framework or to go with Rasmus's no framework framework approach. Language/Framework decisions aside... my main question is about subdomain ( customerx.appname.com vs subdirectory (appname.com/customerx/) models for instances of individual customers' accounts. It seems most people are opting for the former -- is this but a trebd? -- but I see flickr use the latter. The guys at Particletree (i.e., Wufoo) wrote a blog post about it ( http://particletree.com/notebook/subdomains-development-sucks/) years ago to which they still attest. They say the subdirectory model is much easier and faster to develop and deploy. We are developing locally on our macs and will be using Mecurial/Bitbucket for CVS. I'm really lost on this issue as all my searches turn up stuff on SEO/SEM. Is one approach easier that the other? What about security and scalability considerations? I would very much appreciate your opinions as to the pros and cons of each approach. As an aside, does anyone have some advice about rapid PHP deployment, i.e., pushing new features to production daily in micro iterations vs the typical milestone approach? Are there any good tools for this? What about hosts? Thanks all, Tim Tim: My recommendations: 1. No framework. Learn one thing, namely what you want to do and not two (i.e., what you want to do and a framework). I did not know that Rasmus said that, but I listen to what he says. 2. Use directories. They are much simpler to use and easy to create/change/delete/scale/make-secure. -- SEO stuff does not apply here. 3. Investigate Agile development. 4. Host? Roll the dice like the rest of us. Before you can select a hosting provider, define what you want. Are you looking for a cage with power and network connections, a VM that you can load up and manage, or a fully managed server environment? UPS or generator? What about backup and failover? Do you need redundant network connections? There is a wide range of options here that are not easy to evaluate. We have used a variety of different hosts through the years as our needs and requirements changed. Our current one is fully managed, guarantees PCI compliance and is very expensive. But it is still less than the FTE we would have to hire to do it all ourselves. We have more than 100 client sites on that cluster of servers. Depending on your size, it may be worth considering hiring a consultant to walk you through this process the first time. It could save you a lot of mistakes, time and money. Bob McConnell -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP] Web application architecture (subdomain vs. sub directory)
At 9:58 AM -0400 8/26/10, Bob McConnell wrote: From: tedd 4. Host? Roll the dice like the rest of us. Before you can select a hosting provider, define what you want. Are you looking for a cage with power and network connections, a VM that you can load up and manage, or a fully managed server environment? UPS or generator? What about backup and failover? Do you need redundant network connections? There is a wide range of options here that are not easy to evaluate. We have used a variety of different hosts through the years as our needs and requirements changed. Our current one is fully managed, guarantees PCI compliance and is very expensive. But it is still less than the FTE we would have to hire to do it all ourselves. We have more than 100 client sites on that cluster of servers. Depending on your size, it may be worth considering hiring a consultant to walk you through this process the first time. It could save you a lot of mistakes, time and money. Bob McConnell Which I am sure is good advice. Cheers, tedd -- --- http://sperling.com/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On Wed, 2010-08-25 at 13:45 -0500, Tim Martens wrote: Hi Everyone, New to the list. Hello! I'm in the customer discovery phase for a Health IT web application concept I have. My programmer is new to web apps, but not to programming and is set up with LAM(PHP). We're still debating weather to use a framework or to go with Rasmus's no framework framework approach. Language/Framework decisions aside... my main question is about subdomain ( customerx.appname.com vs subdirectory (appname.com/customerx/) models for instances of individual customers' accounts. It seems most people are opting for the former -- is this but a trebd? -- but I see flickr use the latter. The guys at Particletree (i.e., Wufoo) wrote a blog post about it ( http://particletree.com/notebook/subdomains-development-sucks/) years ago to which they still attest. They say the subdirectory model is much easier and faster to develop and deploy. We are developing locally on our macs and will be using Mecurial/Bitbucket for CVS. I'm really lost on this issue as all my searches turn up stuff on SEO/SEM. Is one approach easier that the other? What about security and scalability considerations? I would very much appreciate your opinions as to the pros and cons of each approach. As an aside, does anyone have some advice about rapid PHP deployment, i.e., pushing new features to production daily in micro iterations vs the typical milestone approach? Are there any good tools for this? What about hosts? Thanks all, Tim If you're new to PHP, I would recommend not using a framework for the experience you will gain with the language, as a framework will tend to hide away certain caveats and peculiarities of PHP which could lead to issues further down the line. Most people I know who are great PHP programmers have tended to start without frameworks at first. Having said that, if you're looking for a rapid deployment with a shorter learning curve, then a framework might be better in this situation. Thanks, Ash http://www.ashleysheridan.co.uk
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On 25 August 2010 20:54, Ashley Sheridan a...@ashleysheridan.co.uk wrote: On Wed, 2010-08-25 at 13:45 -0500, Tim Martens wrote: If you're new to PHP, I would recommend not using a framework for the experience you will gain with the language, as a framework will tend to hide away certain caveats and peculiarities of PHP which could lead to issues further down the line. Most people I know who are great PHP programmers have tended to start without frameworks at first. Having said that, if you're looking for a rapid deployment with a shorter learning curve, then a framework might be better in this situation. You could also argue that using a framework is more likely to promote good habits, as there's a bigger chance you'll be forced down good paths. Regards Peter -- hype WWW: http://plphp.dk / http://plind.dk LinkedIn: http://www.linkedin.com/in/plind BeWelcome/Couchsurfing: Fake51 Twitter: http://twitter.com/kafe15 /hype -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On Wed, Aug 25, 2010 at 12:45 PM, Tim Martens tim.mart...@gmail.com wrote: Language/Framework decisions aside... my main question is about subdomain ( customerx.appname.com vs subdirectory (appname.com/customerx/) models for instances of individual customers' accounts. It seems most people are opting for the former -- is this but a trebd? -- but I see flickr use the latter. The guys at Particletree (i.e., Wufoo) wrote a blog post about it ( http://particletree.com/notebook/subdomains-development-sucks/) years ago to which they still attest. subdomains are useful for separating out various applications on a site. for example, suppose you have a client facing application w/ a backend, then a separate application for coordinating development of this app, trac for example. say your main url is blah.com. for the main app you might just take your blah.com proper (this is typical), then for the trac site you have trac.blah.com. within each of these applications the subdirectory approach is taken. basically if you were to use a subdomain approach for a single app it would typically need to be massive to rationalize (unless youre insane). lots of large sites use subdomains to implement distribution. say you have a big image hosting site, all the images are stored on s3, so you might have images.blah.com in that case (note the images are hosted on separate infrastructure). just general guidelines, quite vague, but hopefully helpful. -nathan
RE: [PHP] Web application architecture (subdomain vs. sub directory)
I started out not using a framework... then I started at a company who used a zend like framework, worked there for a bit, then moved on, and started using cake... I found that they were great for what they are... but really simplified things too much, so I created my own framework, incorporating the classes that I use all the time (smarty/fpdf/jquery/tinymce), and with that, I learned a LOT about how things really worked. I would suggest looking at the core of the frameworks to see how things are put together, and how they really work... but maybe make one that is more custom to your application? As for subdomain vs subdirectory, if your using SSL, then you would need a wildcard SSL which is usually more money. Eitherway you choose, you will have to program around it. The app that I created uses subdomains, because we were using CA SSL Certs, and the clients preferred to have their own IP's... long story, not my call, I just program it :P Steven Staples -Original Message- From: Peter Lind [mailto:peter.e.l...@gmail.com] Sent: August 25, 2010 3:01 PM To: a...@ashleysheridan.co.uk Cc: Tim Martens; php-general@lists.php.net Subject: Re: [PHP] Web application architecture (subdomain vs. sub directory) On 25 August 2010 20:54, Ashley Sheridan a...@ashleysheridan.co.uk wrote: On Wed, 2010-08-25 at 13:45 -0500, Tim Martens wrote: If you're new to PHP, I would recommend not using a framework for the experience you will gain with the language, as a framework will tend to hide away certain caveats and peculiarities of PHP which could lead to issues further down the line. Most people I know who are great PHP programmers have tended to start without frameworks at first. Having said that, if you're looking for a rapid deployment with a shorter learning curve, then a framework might be better in this situation. You could also argue that using a framework is more likely to promote good habits, as there's a bigger chance you'll be forced down good paths. Regards Peter -- hype WWW: http://plphp.dk / http://plind.dk LinkedIn: http://www.linkedin.com/in/plind BeWelcome/Couchsurfing: Fake51 Twitter: http://twitter.com/kafe15 /hype -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3089 - Release Date: 08/25/10 02:34:00 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
I am not sure who the end-users are for your website but if you are concerned about scalability, I would definitely go for a sub-domain approach. Assuming you approach a CDN like Akamai and you want to offload the traffic to come from the cloud, it's lot easier for you to integrate with them and to maintain. The subdirectory approach, whereas, is very cumbersome and takes more work at your end to paraphrase the whole set-up should the needs change going forward. Regards, Shreyas On Thu, Aug 26, 2010 at 12:42 AM, Steven Staples sstap...@mnsi.net wrote: I started out not using a framework... then I started at a company who used a zend like framework, worked there for a bit, then moved on, and started using cake... I found that they were great for what they are... but really simplified things too much, so I created my own framework, incorporating the classes that I use all the time (smarty/fpdf/jquery/tinymce), and with that, I learned a LOT about how things really worked. I would suggest looking at the core of the frameworks to see how things are put together, and how they really work... but maybe make one that is more custom to your application? As for subdomain vs subdirectory, if your using SSL, then you would need a wildcard SSL which is usually more money. Eitherway you choose, you will have to program around it. The app that I created uses subdomains, because we were using CA SSL Certs, and the clients preferred to have their own IP's... long story, not my call, I just program it :P Steven Staples -Original Message- From: Peter Lind [mailto:peter.e.l...@gmail.com] Sent: August 25, 2010 3:01 PM To: a...@ashleysheridan.co.uk Cc: Tim Martens; php-general@lists.php.net Subject: Re: [PHP] Web application architecture (subdomain vs. sub directory) On 25 August 2010 20:54, Ashley Sheridan a...@ashleysheridan.co.uk wrote: On Wed, 2010-08-25 at 13:45 -0500, Tim Martens wrote: If you're new to PHP, I would recommend not using a framework for the experience you will gain with the language, as a framework will tend to hide away certain caveats and peculiarities of PHP which could lead to issues further down the line. Most people I know who are great PHP programmers have tended to start without frameworks at first. Having said that, if you're looking for a rapid deployment with a shorter learning curve, then a framework might be better in this situation. You could also argue that using a framework is more likely to promote good habits, as there's a bigger chance you'll be forced down good paths. Regards Peter -- hype WWW: http://plphp.dk / http://plind.dk LinkedIn: http://www.linkedin.com/in/plind BeWelcome/Couchsurfing: Fake51 Twitter: http://twitter.com/kafe15 /hype -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3089 - Release Date: 08/25/10 02:34:00 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- Regards, Shreyas Agasthya
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On Wed, Aug 25, 2010 at 1:20 PM, Shreyas Agasthya shreya...@gmail.comwrote: I am not sure who the end-users are for your website but if you are concerned about scalability, I would definitely go for a sub-domain approach. Assuming you approach a CDN like Akamai and you want to offload the traffic to come from the cloud, it's lot easier for you to integrate with them and to maintain. The subdirectory approach, whereas, is very cumbersome and takes more work at your end to paraphrase the whole set-up should the needs change going forward. bearing in mind you can take a mix--match approach here to avoid insanity. for example on your 'main app' you have a homepage, a user profile page, and a cart page, for conversation sake. again taking blah.com as an example a simple (sane) approach would be blah.com/home blah.com/profile blah.com/cart then imagine you store images on s3, so you have images.blah.com. this is easily incorporated into any of the above urls by simply having image tags with urls of image.blah.com/imageName. no need to have home.blah.com here for example unless the webserver infrastructure was distributed, and even then load balancers could be used to eliminate the call for that. like i was saying youd typically only see this on a big site which operated under an SOA paradigm. take facebook for example, they will have clusters of infrastructure for image management, advertising, search etc. etc. for a simple site sub-directories is the obvious route for a contiguous single application. this really is a question of how large is the site, and what are the load / distribution requirements, IMO. -nathan
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On Wed, Aug 25, 2010 at 01:45:33PM -0500, Tim Martens wrote: Hi Everyone, New to the list. Hello! I'm in the customer discovery phase for a Health IT web application concept I have. My programmer is new to web apps, but not to programming and is set up with LAM(PHP). We're still debating weather to use a framework or to go with Rasmus's no framework framework approach. Language/Framework decisions aside... my main question is about subdomain ( customerx.appname.com vs subdirectory (appname.com/customerx/) models for instances of individual customers' accounts. It seems most people are opting for the former -- is this but a trebd? -- but I see flickr use the latter. The guys at Particletree (i.e., Wufoo) wrote a blog post about it ( http://particletree.com/notebook/subdomains-development-sucks/) years ago to which they still attest. They say the subdirectory model is much easier and faster to develop and deploy. We are developing locally on our macs and will be using Mecurial/Bitbucket for CVS. Use subdirs. If I'm not mistaken, subdomains require web server tweaking that may be beyond your team's expertise. What you're seeing as subdirectories doesn't necessarily strictly represent actual subdirectories on disk. URLs using subdirectories can be (and often are) simply devices to make URLs look prettier. In fact, with some simple web server tweaking (emphasis on simple), your application can map URLs like that to what's actually going on, like: appname.com/whosinsured/customerx = appname.com/index.php?func=whosinsuredcustno=customerx I'm really lost on this issue as all my searches turn up stuff on SEO/SEM. Is one approach easier that the other? What about security and scalability considerations? I would very much appreciate your opinions as to the pros and cons of each approach. I believe this is a red herring. I'm not an expert on SEO, but I believe it works, at its base, simply by HTTP calls to a web server. If the URL is stable and cacheable, then I believe it should suffer no penalty with regard to SEO, no matter how you craft your URLs. Here's where that wouldn't be the case-- if a page has a URL which contains a random or similar key. For example, when subscribing to a list which runs on the mailman package, you are emailed a link which contains some long alphanumeric key on the end. You go to that URL to confirm your wish to join the list. But the link is temporary and expires after a period of time. That type of thing wouldn't work well in an SEO environment. I've read arguments pro and con for what kinds of URLs are SEO-friendly, but I've never seen a search engine make any definitive statement about them. From what I've read, Google doesn't seem to care. As an aside, does anyone have some advice about rapid PHP deployment, i.e., pushing new features to production daily in micro iterations vs the typical milestone approach? Are there any good tools for this? What about hosts? Another issue where the development community is divided. Here's my take on this. It takes a lot of effort to release a new version of a product. Your sources have to be pristine, you have to double-check your builds, you have to compensate for changes in the development environment which may not be echoed on user machines, etc. etc. Moreover, you mustn't dare release a publicly available version of your product without full testing. And if you're doing incremental releases, that means your testers have to test your full product every time a new revision comes down, which can be daily or less. It's a lot of work. Despite the debate on this, I think you'll find most publicly available software is released based on milestones. Paul -- Paul M. Foster -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On Wed, Aug 25, 2010 at 01:45:33PM -0500, Tim Martens wrote: Hi Everyone, New to the list. Hello! I'm in the customer discovery phase for a Health IT web application concept I have. My programmer is new to web apps, but not to programming and is set up with LAM(PHP). We're still debating weather to use a framework or to go with Rasmus's no framework framework approach. I have to echo Steven's comments. A framework makes certain things easier. However, with a n00b programmer, it may well prevent them from digging deeply into the language, because much of the work is done for them by the framework. And Steven's right-- I've found with every single framework I've ever used (going way back to my C language days), the framework ultimately got in my way, to some extent or another. I end up having to code around what the framework's doing to get done what I want. Again, frameworks aren't bad. I use one. I use it because it's one I wrote and suits my needs without getting in my way. I've tried to use it in other environments, and it doesn't always work well in those environments. But it works for the environment in which I code. Paul -- Paul M. Foster -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Web application architecture (subdomain vs. sub directory)
Thanks for all your answers. To clarify my question, I'm looking for advice regarding how best to set up users for a web app, e.g., username.myapp.comvs myapp.com/username and the pros and cons of each. All users will be using essentially the same app that will have their data in their account. I can see the logic of setting up subdomain for things like a universal login and, say, metrics for example. Is javascripting more difficult across subdomains? Is one approach beter in terms of security? Essentially the entire app will be running on https. Thanks again! Tim On Wed, Aug 25, 2010 at 2:07 PM, Nathan Nobbe quickshif...@gmail.comwrote: On Wed, Aug 25, 2010 at 12:45 PM, Tim Martens tim.mart...@gmail.comwrote: Language/Framework decisions aside... my main question is about subdomain ( customerx.appname.com vs subdirectory (appname.com/customerx/) models for instances of individual customers' accounts. It seems most people are opting for the former -- is this but a trebd? -- but I see flickr use the latter. The guys at Particletree (i.e., Wufoo) wrote a blog post about it ( http://particletree.com/notebook/subdomains-development-sucks/) years ago to which they still attest. subdomains are useful for separating out various applications on a site. for example, suppose you have a client facing application w/ a backend, then a separate application for coordinating development of this app, trac for example. say your main url is blah.com. for the main app you might just take your blah.com proper (this is typical), then for the trac site you have trac.blah.com. within each of these applications the subdirectory approach is taken. basically if you were to use a subdomain approach for a single app it would typically need to be massive to rationalize (unless youre insane). lots of large sites use subdomains to implement distribution. say you have a big image hosting site, all the images are stored on s3, so you might have images.blah.com in that case (note the images are hosted on separate infrastructure). just general guidelines, quite vague, but hopefully helpful. -nathan
Re: [PHP] Web application architecture (subdomain vs. sub directory)
On Wed, 2010-08-25 at 21:01 +0200, Peter Lind wrote: On 25 August 2010 20:54, Ashley Sheridan a...@ashleysheridan.co.uk wrote: On Wed, 2010-08-25 at 13:45 -0500, Tim Martens wrote: If you're new to PHP, I would recommend not using a framework for the experience you will gain with the language, as a framework will tend to hide away certain caveats and peculiarities of PHP which could lead to issues further down the line. Most people I know who are great PHP programmers have tended to start without frameworks at first. Having said that, if you're looking for a rapid deployment with a shorter learning curve, then a framework might be better in this situation. You could also argue that using a framework is more likely to promote good habits, as there's a bigger chance you'll be forced down good paths. +1 -- Blessings, David M. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
