The priority of the Symfony’s contributors has always been to initially stabilize the features of the existing version of this PHP based framework and then work on the new ones. This is clear very much clear from the fact that before release of new functionalities with Symfony 3.1, the contributors of the framework came up with its 3.0 version initially, which had no more features than its predecessor 2.8 but only removed deprecations from it. It was just a stabilized version of the early Symfony 2.8. And now, the PHP framework contributors are out with new features to captivate the interests of the developers and businesses alike. There are many new, exciting features in this latest release update of Symfony that are expected to bring a lot of improvements in the present Symfony development processes.
Let us have a look at what are some of the new, interesting features present in Symfony 3.1
Lightweight Directory Access Protocol (LDAP):
LDAP is a trusted industry protocol for maintaining and assessing the services related to distributed directory information over the network. Symfony introduced this feature in its 3.0 release last year and is now revising it with major updates in 3.1 version. These updates include configuring the LDAP options for connection, including write support for LDAP components, adding default service name of the security components etc.
Security component is responsible for protecting the web application from security exploits and hence, provides various tools to integrate tight security within the application. The component exercises security control on the app with four things – security-HTTP, security-core, security-csrf and security-acl.
However in Symfony 3.1, this component comes with following updates
– Auth trust resolver for finding the anonymous in ContextListener
– Get/set the authentication “target_path” with new TargetPathTrait
In Symfony, YAML is extensively used to convert the YAML strings into PHP arrays and hence, find its applications for configuration files and page settings. There are few major updates expected in YAML in Symfony 3.1 like customization of parse behavior with flags, support for dumping and parsing the date and time objects etc.
The purpose of console component is to create command-line interfaces and to run commands for recurring tasks right from console. The tasks can be the cron jobs, batch jobs, import and export functions etc. In the previous versions of Symfony, these commands used in console component could not be registered privately, but now in 3.1 this is made possible. Now, the private commands are allowed for private registration. Now the FormatterHelper class has the truncate method and ApplicationTester is available for stdout and stderr testing.
The Process Component:
The PROCESS component has been updated in Symfony 3.1 with features like callback when output gets disabled, support for traversable input and addition of IteratorAggregate for output streaming. This process component is defined in Symfony to take care of the differences between the various platforms at the time of command execution and to provide object- oriented abstraction for independent process execution in PHP.
Apart from this, there are also a few improvements with HTTPKernel, Serializer and Form components in the latest version of Symfony 3.1, which still under the process and is worked upon by the Symfony contributors who are putting their efforts for a perfect upgrade over the early Symfony versions.
Hence, Symfony 3.1 development is the future way for you to go, if you are looking to develop web applications for your needs with Symfony. There are few resources online that can guide you to the ultimate Symfony web application development with version 3.1 as of now, however, you can excel on it in the coming time as the update gets released to its full-fledged form.