May 22, 2012

Laravel 3.2 released

Laravel migrated core request/response handling to SymfonyA PHP framework and component library — enterprise web apps and APIs across Europe.'s HttpFoundation component.

What it was for

LaravelInstead of maintaining its own HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. layer, Laravel adopted SymfonyA PHP framework and component library — enterprise web apps and APIs across Europe.'s battle-tested request/response objects. For developers: handling cookies, headers, and responses works the same way across SymfonyA PHP framework and component library — enterprise web apps and APIs across Europe., Laravel, and other PHP tools — less duplicated code in the PHP ecosystem.

Why it's here

This is the clearest example of Laravel embracing SymfonyA PHP framework and component library — enterprise web apps and APIs across Europe. instead of maintaining parallel HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. stacks.

Why it mattered

Shared components meant PHP developers could move between Laravel, SymfonyA PHP framework and component library — enterprise web apps and APIs across Europe., and DrupalA PHP-based CMS known for flexibility — popular for large government and enterprise sites. with familiar HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. primitives.

What it solved

Maintaining custom request/response code duplicated effort across the PHP ecosystem.

Media

  • Laravel
    ImageLaravel

    Laravel, Public domain, via Wikimedia Commons

Related