By Adam Griffiths. CodeIgniter is an open source PHP framework with a small footprint and exceptional performance. It gives you a rich set of libraries for common tasks, with a simple interface to access them. There are several unexplored aspects of CodeIgniter that can help developers build applications more easily and quickly.
|Published (Last):||25 February 2008|
|PDF File Size:||13.54 Mb|
|ePub File Size:||18.7 Mb|
|Price:||Free* [*Free Regsitration Required]|
Want to read Slashdot from your mobile device? Point it at m. Perhaps they don't pop up every other week, you've just never heard of most of them since you're probably not a PHP developer. Nah, not every other week, but every year it's a different framework that is the "Coolest thing ever and everyone who isn't using it is dumb" according to most of the PHP developers I know and work around. That was going to rock the web development world after the whole Ruby on Rails thing died down.
Before Cake, Zend was all the rage. Maybe it is snails because it leaves a sticky, messy trail wherever it goes? It's mantras like these that lead to so much insecure web code being written.
You should always be equally worried about security no matter if you're using a framework or homegrown code. As with any programming, you can still create security problems for yourself even using a popular framework.
Linux is more popular, OpenBSD is arguably more secure. Security often offends the sensibilities that would make a thing popular. We are comparing a solid, mature framework, built and maintained by professionals, used on hundreds or thousands of sites, with a public bug reporting system to an ad hoc collection of code written by one person. I don't really get why people use a framework for php at all.
The whole point of php is so you can write web app code anyway you like. Writing to CI spec is such a waste of time since you literally have to track their APIs back to the source, and the functions defining these APIs are all over the place.
Inject your own modules or applications into the existing session is hours of work just to track down what the hell they did. All the customer code are sitting in an include container, that handle sessions. I beg to differ, there is no difference tracking down a piece of code in your mountain of framework definition and tracking down a piece of code in a mountain of procedural spaghetti code.
It doesn't matter how large your project is, as long as you maintain a sane c. Frameworks trade the time needed to learn the framework for time writing your own code. The presumption that you will learn the framework as well as your own code is questionable at best. Odds are you won't need everything in the framework.
The benefits of a wide community using the framework, and, if the framework is well maintained, having it tweaked as the community reports problems, is a big plus; but it is counter-featured by problems and vulnerabilities affecting wide swaths of users until fixed or. If that were true there wouldn't be the dozens upon dozens of frameworks that probably share little to no code between them. In fact, these frameworks are nothing but a constant reinventing of the wheel. I'm not advocating everyone create their own framework unless they really have a good use case for doing so and thus you're arguing against a point I wasn't making.
And honestly, if you're that concerned about scalability, you're not going to be using PHP. I know that it isn't always the smoothest, but Facebook is PHP, and is pretty fricken huge. Sort of. According to what an employee told me last week, lots of the core services are written in other languages, and then PHP is the glue that queries those services and builds the page itself.
They then have found that that really isn't fast enough for what they want, so they've written their own compiler Hip Hop [github. In my experience, the only decent PHP framework is Wordpress. Seriously, you can do a hell of a lot with very little work just by creating a theme and using three or four plugins. It's hard to beat that for smaller sites. I am sorry, but the framework still supports PHP version 4. Support for PHP 4 was ended at the end of Any framework that doesn't take advantage of the nice new features in PHP 5 bound to be full of kludges and outdated code.
That is just my reaction based on when I was comparing PHP frameworks, I didn't dig into their code so maybe I am wrong. I haven't dug in too far, since I'm paid to spend my time working on my company's proprietary framework, but CodeIgniters seems to have done a pretty good job in how they've gone about maintaining PHP4 support.
Clever solutions rather than outdated ones, to put it briefly. I believe CI 2. Why is waiting until the next major revision to break compatibility a bad thing? PHP 5 adoption is taking a long time, too. There are still webhosts that only offer 4. They suck, but they're out there. Highly recommended for anyone out there looking for a PHP framework that actually makes sense. Wish I had mod points. It is much, much better than CI. Kohana's documentation is giving me a server error.
Follow Slashdot on LinkedIn. RickJWagner writes "CodeIgniter is a multi-purpose, open source PHP web application framework that can dramatically reduce the amount of coding required in developing a full-featured website. This book promises to introduce the reader to the most productive APIs and demonstrate their usage with minimal code snippets. In that regard, I think the book lives up to its promise.
CodeIgniter 1. This discussion has been archived. No new comments can be posted. More Login. PHP frameworks Score: 1. How crappy can they all be that a new one pops up every other week? Re: Score: 2 , Informative.
CodeIgniter has been around for a while, dude. Re: Score: 1. Parent Share twitter facebook linkedin. Re: Score: 2. I was the. Score: 5 , Funny.
The cover photo is of Naturally, the immediate association is with "a snail's pace. Share twitter facebook linkedin. PHP code? I don't know. I'm so confused. Re:Web application framework?
Score: 5 , Insightful. You don't need to worry as much about security vulnerabilities. Re: Score: 3 , Insightful. If you are using a popular framework, there are many people who can discover and fix vulnerabilities. If you write your own framework, you are responsible for handling that all yourself. Well, as with any other task, if you have qualified people assisting you, you don't have to worry as much about the task being completed successfully.
I think it would be better phrase " It allows you to be more confident in your application's security ". You're semantically correct, a developer's level of concern for security shouldn't change. So I just want to make sure I have this right: less worried! I will make sure to be more confident that my applications are secure, while still maintaining the same level of worry that they may be insecure. In fact, popular rarely equates to secure.
We are comparing a solid, mature framework, built and maintained by professionals, used on hundreds or thousands of sites, with a public bug reporting system to an ad hoc collection of code written by one person so your analogy doesn't hold.
Your incomplete understanding of my analogy does not invalidate it. Not so cut and dry Score: 2. Score: 1. It's about not reinventing the wheel. You could argue that the people creating these frameworks are reinventing the wheel. The point is, when you create your own framework YOU are reinventing the wheel.
Codeigniter 1.7 Professional Development
Slashdot Top Deals
CodeIgniter 1. Adam Griffiths. This book is a practical guide that takes you through a number of techniques. Each chapter builds upon knowledge from the previous chapter. Step-by-step instructions with examples and illustrative screenshots ensure that you gain a firm grasp of the topic being explained.
CodeIgniter 1.7 Professional Development
Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Other editions. Enlarge cover. Error rating book.
Por Adam Griffiths. CodeIgniter is an open source PHP framework with a small footprint and exceptional performance. It gives you a rich set of libraries for common tasks, with a simple interface to access them. There are several unexplored aspects of CodeIgniter that can help developers build applications more easily and quickly. In this book, you will learn the intricacies of the framework and explore some of its hidden gems. If you want to get the most out of CodeIgniter, this book is for you.