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 <sstaples@xxxxxxxx> 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.lind@xxxxxxxxx] > > Sent: August 25, 2010 3:01 PM > > To: ash@xxxxxxxxxxxxxxxxxxxx > > Cc: Tim Martens; php-general@xxxxxxxxxxxxx > > Subject: Re: Web application architecture (subdomain vs. sub > > directory) > > > > On 25 August 2010 20:54, Ashley Sheridan <ash@xxxxxxxxxxxxxxxxxxxx> > 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
