Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit d802d42

Browse filesBrowse files
fabpotfabpot
committed
updated code for Symfony 2.3 and made minor tweaks to the text
1 parent f3c151c commit d802d42
Copy full SHA for d802d42

File tree

Expand file treeCollapse file tree

10 files changed

+57
-62
lines changed
Filter options
Expand file treeCollapse file tree

10 files changed

+57
-62
lines changed

‎book/part01.rst

Copy file name to clipboardExpand all lines: book/part01.rst
+13-12Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -53,20 +53,21 @@ Symfony2 Components.
5353
based on the Symfony2 Components. The code is rather slim and it leverages
5454
many aspects of the Symfony2 Components.
5555

56-
Many modern web frameworks call themselves MVC frameworks. We won't talk about
57-
MVC here as the Symfony2 Components are able to create any type of frameworks,
58-
not just the ones that follow the MVC architecture. Anyway, if you have a look
59-
at the MVC semantics, this book is about how to create the Controller part of
60-
a framework. For the Model and the View, it really depends on your personal
61-
taste and I will let you use any existing third-party libraries (Doctrine,
62-
Propel, or plain-old PDO for the Model; PHP or Twig for the View).
56+
Many modern web frameworks advertize themselves as being MVC frameworks. We
57+
won't talk about the MVC pattern as the Symfony2 Components are able to create
58+
any type of frameworks, not just the ones that follow the MVC architecture.
59+
Anyway, if you have a look at the MVC semantics, this book is about how to
60+
create the Controller part of a framework. For the Model and the View, it
61+
really depends on your personal taste and I will let you use any existing
62+
third-party libraries (Doctrine, Propel, or plain-old PDO for the Model; PHP
63+
or Twig for the View).
6364

6465
When creating a framework, following the MVC pattern is not the right goal.
65-
The main goal should be the Separation of Concerns; I actually think that this
66-
is the only design pattern that you should really care about. The fundamental
67-
principles of the Symfony2 Components are focused on the HTTP specification.
68-
As such, the frameworks that we are going to create should be more accurately
69-
labelled as HTTP frameworks or Request/Response frameworks.
66+
The main goal should be the **Separation of Concerns**; I actually think that
67+
this is the only design pattern that you should really care about. The
68+
fundamental principles of the Symfony2 Components are focused on the HTTP
69+
specification. As such, the frameworks that we are going to create should be
70+
more accurately labelled as HTTP frameworks or Request/Response frameworks.
7071

7172
Before we start
7273
---------------

‎book/part02.rst

Copy file name to clipboardExpand all lines: book/part02.rst
+9-8Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ dependency for the project:
129129
130130
{
131131
"require": {
132-
"symfony/http-foundation": "2.1.*"
132+
"symfony/http-foundation": "~2.3"
133133
}
134134
}
135135
@@ -170,8 +170,8 @@ first outputs the HTTP headers followed by the content).
170170
Before the ``send()`` call, we should have added a call to the
171171
``prepare()`` method (``$response->prepare($request);``) to ensure that
172172
our Response were compliant with the HTTP specification. For instance, if
173-
we were to call the page with the ``HEAD`` method, it would have removed
174-
the content of the Response.
173+
we were to call the page with the ``HEAD`` method, it would remove the
174+
content of the Response.
175175

176176
The main difference with the previous code is that you have total control of
177177
the HTTP messages. You can create whatever request you want and you are in
@@ -275,11 +275,12 @@ secure? The ``$_SERVER['HTTP_X_FORWARDED_FOR']`` value cannot be trusted as it
275275
can be manipulated by the end user when there is no proxy. So, if you are
276276
using this code in production without a proxy, it becomes trivially easy to
277277
abuse your system. That's not the case with the ``getClientIp()`` method as
278-
you must explicitly trust this header by calling ``trustProxyData()``::
278+
you must explicitly trust your reverse proxies by calling
279+
``setTrustedProxies()``::
279280

280281
<?php
281282

282-
Request::trustProxyData();
283+
Request::setTrustedProxies(array('10.0.0.1'));
283284

284285
if ($myIp == $request->getClientIp(true)) {
285286
// the client is a known one, so give it some more privilege
@@ -302,9 +303,9 @@ Using just the Symfony2 HttpFoundation component already allows you to write
302303
better and more testable code. It also allows you to write code faster as many
303304
day-to-day problems have already been solved for you.
304305

305-
As a matter of fact, projects like Drupal have adopted (for the upcoming
306-
version 8) the HttpFoundation component; if it works for them, it will
307-
probably work for you. Don't reinvent the wheel.
306+
As a matter of fact, projects like Drupal have adopted the HttpFoundation
307+
component; if it works for them, it will probably work for you. Don't reinvent
308+
the wheel.
308309

309310
I've almost forgot to talk about one added benefit: using the HttpFoundation
310311
component is the start of better interoperability between all frameworks and

‎book/part03.rst

Copy file name to clipboardExpand all lines: book/part03.rst
+6-6Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -65,8 +65,8 @@ And for the "Goodbye" page::
6565

6666
We have indeed moved most of the shared code into a central place, but it does
6767
not feel like a good abstraction, doesn't it? First, we still have the
68-
``send()`` method in all pages, then our pages does not look like templates,
69-
and we are still not able to test this code properly.
68+
``send()`` method in all pages, then our pages do not look like templates, and
69+
we are still not able to test this code properly.
7070

7171
Moreover, adding a new page means that we need to create a new PHP script,
7272
which name is exposed to the end user via the URL
@@ -140,9 +140,9 @@ To access a page, you must now use the ``front.php`` script:
140140
able to type ``http://example.com/hello?name=Fabien``, which looks much
141141
better.
142142

143-
So, the trick is the usage of the ``Request::getPathInfo()`` method which
144-
returns the path of the Request by removing the front controller script name
145-
including its sub-directories (only if needed -- see above tip).
143+
The trick is the usage of the ``Request::getPathInfo()`` method which returns
144+
the path of the Request by removing the front controller script name including
145+
its sub-directories (only if needed -- see above tip).
146146

147147
.. tip::
148148

@@ -205,7 +205,7 @@ And the ``hello.php`` script can now be converted to a template::
205205

206206
Hello <?php echo htmlspecialchars($name, ENT_QUOTES, 'UTF-8') ?>
207207

208-
We have our framework for today::
208+
We have the first version of our framework::
209209

210210
<?php
211211

‎book/part04.rst

Copy file name to clipboardExpand all lines: book/part04.rst
+3-10Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,8 @@ update`` command to install it:
6161
6262
{
6363
"require": {
64-
"symfony/http-foundation": "2.1.*",
65-
"symfony/routing": "2.1.*"
64+
"symfony/http-foundation": "~2.3",
65+
"symfony/routing": "~2.3"
6666
}
6767
}
6868
@@ -181,7 +181,7 @@ There are a few new things in the code::
181181

182182
Hello <?php echo htmlspecialchars($name, ENT_QUOTES, 'UTF-8') ?>
183183

184-
* Routes configuration has been moved to its own file:
184+
* Route configuration has been moved to its own file:
185185

186186
.. code-block:: php
187187
@@ -232,11 +232,4 @@ generate absolute URLs::
232232

233233
echo $dumper->dump();
234234

235-
Want even more performance? Dump your routes as a set of Apache rewrite
236-
rules::
237-
238-
$dumper = new Routing\Matcher\Dumper\ApacheMatcherDumper($routes);
239-
240-
echo $dumper->dump();
241-
242235
.. _`documentation`: http://symfony.com/doc/current/components/routing.html

‎book/part05.rst

Copy file name to clipboardExpand all lines: book/part05.rst
+6-6Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,8 @@ As the rendering is now done by an external function (``render_template()``
3333
here), we need to pass to it the attributes extracted from the URL. We could
3434
have passed them as an additional argument to ``render_template()``, but
3535
instead, let's use another feature of the ``Request`` class called
36-
*attributes*: Request attributes lets you attach additional information about
37-
the Request that is not directly related to the HTTP Request data.
36+
*attributes*: Request attributes is a way to attach additional information
37+
about the Request that is not directly related to the HTTP Request data.
3838

3939
You can now create the ``render_template()`` function, a generic controller
4040
that renders a template when there is no specific logic. To keep the same
@@ -177,10 +177,10 @@ framework does not need to be modified in any way, just create a new
177177
return $routes;
178178

179179
The ``is_leap_year()`` function returns ``true`` when the given year is a leap
180-
year, ``false`` otherwise. If the year is null, the current year is tested.
181-
The controller is simple: it gets the year from the request attributes, pass
182-
it to the `is_leap_year()`` function, and according to the return value it
183-
creates a new Response object.
180+
year, ``false`` otherwise. If the year is ``null``, the current year is
181+
tested. The controller is simple: it gets the year from the request
182+
attributes, pass it to the `is_leap_year()`` function, and according to the
183+
return value it creates a new Response object.
184184

185185
As always, you can decide to stop here and use the framework as is; it's
186186
probably all you need to create simple websites like those fancy one-page

‎book/part06.rst

Copy file name to clipboardExpand all lines: book/part06.rst
+4-4Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,9 +41,9 @@ component::
4141

4242
{
4343
"require": {
44-
"symfony/http-foundation": "2.1.*",
45-
"symfony/routing": "2.1.*",
46-
"symfony/http-kernel": "2.1.*"
44+
"symfony/http-foundation": "~2.3",
45+
"symfony/routing": "~2.3",
46+
"symfony/http-kernel": "~2.3"
4747
}
4848
}
4949

@@ -145,7 +145,7 @@ method is not defined, an argument has no matching attribute, ...).
145145

146146
With the great flexibility of the default controller resolver, you might
147147
wonder why someone would want to create another one (why would there be an
148-
interface if not). Two examples: in Symfony2, ``getController()`` is
148+
interface if not?). Two examples: in Symfony2, ``getController()`` is
149149
enhanced to support `controllers as services`_; and in
150150
`FrameworkExtraBundle`_, ``getArguments()`` is enhanced to support
151151
parameter converters, where request attributes are converted to objects

‎book/part07.rst

Copy file name to clipboardExpand all lines: book/part07.rst
+4-4Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -89,12 +89,12 @@ be autoloaded, update the ``composer.json`` file:
8989
9090
{
9191
"require": {
92-
"symfony/http-foundation": "2.1.*",
93-
"symfony/routing": "2.1.*",
94-
"symfony/http-kernel": "2.1.*"
92+
"symfony/http-foundation": "~2.3",
93+
"symfony/routing": "~2.3",
94+
"symfony/http-kernel": "~2.3"
9595
},
9696
"autoload": {
97-
"psr-0": { "Simplex": "src/", "Calendar": "src/" }
97+
"psr-0": { "Simplex\\": "src/", "Calendar\\": "src/" }
9898
}
9999
}
100100

‎book/part09.rst

Copy file name to clipboardExpand all lines: book/part09.rst
+5-5Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,13 @@ version of this pattern:
2121
2222
{
2323
"require": {
24-
"symfony/http-foundation": "2.1.*",
25-
"symfony/routing": "2.1.*",
26-
"symfony/http-kernel": "2.1.*",
27-
"symfony/event-dispatcher": "2.1.*"
24+
"symfony/http-foundation": "~2.3",
25+
"symfony/routing": "~2.3",
26+
"symfony/http-kernel": "~2.3",
27+
"symfony/event-dispatcher": "~2.3"
2828
},
2929
"autoload": {
30-
"psr-0": { "Simplex": "src/", "Calendar": "src/" }
30+
"psr-0": { "Simplex\\": "src/", "Calendar\\": "src/" }
3131
}
3232
}
3333

‎book/part11.rst

Copy file name to clipboardExpand all lines: book/part11.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ The error controller reads as follows::
110110
Voilà! Clean and customizable error management without efforts. And of course,
111111
if your controller throws an exception, HttpKernel will handle it nicely.
112112

113-
In part 2, we have talked about the ``Response::prepare()`` method, which
113+
In chapter two, we talked about the ``Response::prepare()`` method, which
114114
ensures that a Response is compliant with the HTTP specification. It is
115115
probably a good idea to always call it just before sending the Response to the
116116
client; that's what the ``ResponseListener`` does::

‎book/part12.rst

Copy file name to clipboardExpand all lines: book/part12.rst
+6-6Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -95,14 +95,14 @@ container:
9595
9696
{
9797
"require": {
98-
"symfony/http-foundation": "2.1.*",
99-
"symfony/routing": "2.1.*",
100-
"symfony/http-kernel": "2.1.*",
101-
"symfony/event-dispatcher": "2.1.*",
102-
"symfony/dependency-injection": "2.1.*"
98+
"symfony/http-foundation": "~2.3",
99+
"symfony/routing": "~2.3",
100+
"symfony/http-kernel": "~2.3",
101+
"symfony/event-dispatcher": "~2.3",
102+
"symfony/dependency-injection": "~2.3"
103103
},
104104
"autoload": {
105-
"psr-0": { "Simplex": "src/", "Calendar": "src/" }
105+
"psr-0": { "Simplex\\": "src/", "Calendar\\": "src/" }
106106
}
107107
}
108108

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.