Go back

A Year With Symfony Writing Healthy Reusable Symfony2 Code(1st Edition)

Authors:

Matthias Noback

Free a year with symfony writing healthy reusable symfony2 code 1st edition matthias noback 9082120119,
6 ratings
Cover Type:Hardcover
Condition:Used

In Stock

Include with your book

Free shipping: April 04, 2024
Access to 3 Million+ solutions Free
Ask 10 Questions from expert 200,000+ Expert answers
7 days-trial

Total Price:

$0

List Price: $72.00 Savings: $72(100%)

Book details

ISBN: 9082120119, 978-9082120110

Book publisher: Matthias Noback (September 4, 2013)

Get your hands on the best-selling book A Year With Symfony Writing Healthy Reusable Symfony2 Code 1st Edition for free. Feed your curiosity and let your imagination soar with the best stories coming out to you without hefty price tags. Browse SolutionInn to discover a treasure trove of fiction and non-fiction books where every page leads the reader to an undiscovered world. Start your literary adventure right away and also enjoy free shipping of these complimentary books to your door.

A Year With Symfony Writing Healthy Reusable Symfony2 Code 1st Edition Summary: I've written A Year With Symfony for you, a developer who will work with Symfony2 for more than a month (and probably more than a year). You may have started reading your way through the official documentation ("The Book"), the cookbook, some blogs, or an online tutorial. You know now how to create a Symfony2 application, with routing, controllers, entities or documents, Twig templates and maybe some unit tests. But after these basic steps, some concerns will raise about...The reusability of your code - How should you structure your code to make it reusable in a future project? Or even in the same project, but with a different view or in a console command?The quality of the internal API you have knowingly or unknowingly created - What can you do to ensure that your team members will understand your code, and will use it in the way it was meant to be used? How can you make your code flexible enough to be used in situations resembling the one you wrote it for?The level of security of your application - Symfony2 and Doctrine seem to automatically make you invulnerable for well-known attacks on your web application, like XSS, CSRF and SQL injection attacks. But can you completely rely on the framework? And what steps should you take to fix some of the remaining issues?The inner workings of Symfony2 - When you take one step further from creating just controllers and views, you will soon need to know more about the HttpKernel which is the heart of a Symfony2 application. How does it know what controller should be used, and which template? And how can you override any decision that's made while handling a request?