Skip to content
Commits on Sep 30, 2012
  1. @benja-M-1 @fabpot
Commits on May 15, 2012
  1. @fabpot

    fixed phpdoc @param alignment

    fabpot committed
Commits on Jul 20, 2011
  1. @fabpot
Commits on Jul 11, 2011
  1. @francisbesset

    Moved managing cookies of HeaderBag in ResponseHeaderBag

    francisbesset committed
    By example, a cookie can't be set in a request
Commits on Jul 5, 2011
  1. @fabpot
Commits on May 15, 2011
  1. @fabpot
  2. @fabpot

    [HttpFoundation] fixed a warning

    fabpot committed
  3. @fabpot
  4. @fabpot
Commits on Apr 26, 2011
  1. @vicb
Commits on Mar 6, 2011
  1. @fabpot
Commits on Feb 27, 2011
  1. @pborreli
Commits on Feb 12, 2011
  1. @hhamon @fabpot

    [HttpFoundation] fixed phpdoc

    hhamon committed with fabpot
Commits on Jan 31, 2011
  1. @fabpot
Commits on Jan 23, 2011
  1. @avalanche123 @fabpot
Commits on Jan 18, 2011
  1. @blue-eyes @fabpot
Commits on Jan 15, 2011
  1. @schmittjoh @fabpot
Commits on Nov 25, 2010
  1. @fabpot

    made some method name changes to have a better coherence throughout t…

    fabpot committed
    …he framework
    
    When an object has a "main" many relation with related "things" (objects,
    parameters, ...), the method names are normalized:
    
     * get()
     * set()
     * all()
     * replace()
     * remove()
     * clear()
     * isEmpty()
     * add()
     * register()
     * count()
     * keys()
    
    The classes below follow this method naming convention:
    
     * BrowserKit\CookieJar -> Cookie
     * BrowserKit\History -> Request
     * Console\Application -> Command
     * Console\Application\Helper\HelperSet -> HelperInterface
     * DependencyInjection\Container -> services
     * DependencyInjection\ContainerBuilder -> services
     * DependencyInjection\ParameterBag\ParameterBag -> parameters
     * DependencyInjection\ParameterBag\FrozenParameterBag -> parameters
     * DomCrawler\Form -> FormField
     * EventDispatcher\Event -> parameters
     * Form\FieldGroup -> Field
     * HttpFoundation\HeaderBag -> headers
     * HttpFoundation\ParameterBag -> parameters
     * HttpFoundation\Session -> attributes
     * HttpKernel\Profiler\Profiler -> DataCollectorInterface
     * Routing\RouteCollection -> Route
     * Security\Authentication\AuthenticationProviderManager -> AuthenticationProviderInterface
     * Templating\Engine -> HelperInterface
     * Translation\MessageCatalogue -> messages
    
    The usage of these methods are only allowed when it is clear that there is a
    main relation:
    
     * a CookieJar has many Cookies;
    
     * a Container has many services and many parameters (as services is the main
       relation, we use the naming convention for this relation);
    
     * a Console Input has many arguments and many options. There is no "main"
       relation, and so the naming convention does not apply.
    
    For many relations where the convention does not apply, the following methods
    must be used instead (where XXX is the name of the related thing):
    
     * get()      -> getXXX()
     * set()      -> setXXX()
     * all()      -> getXXXs()
     * replace()  -> setXXXs()
     * remove()   -> removeXXX()
     * clear()    -> clearXXX()
     * isEmpty()  -> isEmptyXXX()
     * add()      -> addXXX()
     * register() -> registerXXX()
     * count()    -> countXXX()
     * keys()
Commits on Nov 21, 2010
  1. @ornicar @fabpot
Commits on Nov 18, 2010
  1. @fabpot

    changed Cache-Control default value behavior

    fabpot committed
    The PHP native cache limiter feature has been disabled as this is now managed
    by the HeaderBag class directly instead (see below.)
    
    The HeaderBag class uses the following rules to define a sensible and
    convervative default value for the Response 'Cache-Control' header:
    
     * If no cache header is defined ('Cache-Control', 'ETag', 'Last-Modified',
       and 'Expires'), 'Cache-Control' is set to 'no-cache';
    
     * If 'Cache-Control' is empty, its value is set to "private, max-age=0,
       must-revalidate";
    
     * But if at least one 'Cache-Control' directive is set, and no 'public' or
       'private' directives have been explicitely added, Symfony2 adds the
       'private' directive automatically (except when 's-maxage' is set.)
    
    So, remember to explicitly add the 'public' directive to 'Cache-Control' when
    you want shared caches to store your application resources:
    
        // The Response is private by default
        $response->setEtag($etag);
        $response->setLastModified($date);
        $response->setMaxAge(10);
    
        // Change the Response to be public
        $response->setPublic();
    
        // Set cache settings in one call
        $response->setCache(array(
            'etag'          => $etag,
            'last_modified' => $date,
            'max_age'       => 10,
            'public'        => true,
        ));
Commits on Nov 3, 2010
  1. @schmittjoh @fabpot
Commits on Oct 28, 2010
  1. @jfphilippe @fabpot

    [HttpFoundation] updated get() signature to get($key, $default = null…

    jfphilippe committed with fabpot
    …, $first = true)
    
    This is more consistent with the get() method of ParameterBag
Commits on Oct 18, 2010
  1. @kriswallsmith @fabpot
Commits on Aug 26, 2010
  1. @fabpot
Commits on Aug 20, 2010
  1. @fabpot
Something went wrong with that request. Please try again.