Releases for sf 1.2
| Version |
License |
API |
Released |
|
1.2.2stable
|
MIT license |
1.2.0stable
|
18/09/2009 |
|
1.2.0stable
|
MIT license |
1.2.0stable
|
30/08/2009 |
Changelog for release 1.2.2 - 18/09/2009
Other releases
Release 1.2.2 - 18/09/2009
Release 1.2.0 - 30/08/2009
Cross Application Routing
More info at : http://rabaix.net/en/articles/2009/07/13/cross-link-application-with-symfony-part-2
Installation
The configuration format has been updated. You can now specify the routes to be loaded
for each environnement.
Enable the feature, edit your app.yml
all:
swToolbox:
cross_link_application:
frontend:
enabled: on # enable the feature
load:
backend:
routes: # routes to load, leave empty will load all the routes
- homepage
- edit_blog
env: # define the environment
dev: rabaix.net/backend.php # define the full path for the dev environnement
prod: rabaix.net/backend # define the full path for the prod environnement
backend:
enabled: on
load:
frontend:
routes:
- homepage
- edit_blog
env:
dev: rabaix.net/frontend_dev.php
prod: rabaix.net
- Note : The configuration format has been updated !
Edit your factories.yml
all:
routing:
class: swPatternRouting
In your frontend's template, you can access to a backend route like this
<?php link_to('Edit Blog Post', '@backend.edit_post?id='.$blog->getId()) ?>
that's all !!
Performance
If you load too many routes, the application can be very slow in development. You can
save seconds by simply turn off the debug options.
[yml]
all:
routing:
class: swPatternRouting
param:
debug: false # default is true in dev mode.
Of course don't forget to reload the cache once the routing.yml file is updated
Please take a note that the default cache handler for routing is the sfFileCache.
This can also slow down the application because php has to serialize and unserialize
the cache.
Some input :
- 1150 routes generates a 3MBytes cache file
- 356 routes generates a 1MBytes cache file
So in production you might need to tweak the routing caching strategy