[application/connect] simplify connection logic ``application.connect`` now either sets a full featured ``DBAPISession`` to the ``WebRequest`` object or raises ``AuthenticationError``. The creation and usage of a fake DBAPISession is now handled by ``main_handle_request`` when needed. This means that fake DBAPISession are no longer tracked by the session manager and that user are not given anyway to retrieve them for a later request. This fake DBAPISession is still passed to ``core_handle`` because multiple cubes like registration or forgotten password need this behavior. We would like to get ride of it in the future. This clarification of the connection API greatly simplifies ``DBAPISession`` retrieval//creation process opening the way to improvements in this area. Related to #2503918

     1

Javascript Coding Standards

     2

---------------------------

     3

     4

(Draft, to be continued)

     5

     6

:Naming: camelCase, except for CONSTANTS

     7

     8

Indentation rules

     9

~~~~~~~~~~~~~~~~~

    10

- espace avant accolade ouvrante

    11

    12

- retour à la ligne après accolade ouvrante (éventuellement pas

    13

  de retour à la ligne s'il y a tout sur la même ligne, mais ce n'est

    14

  pas le cas ici.

    15

    16

- no tabs

    17

    18

    19

Documentation

    20

~~~~~~~~~~~~~

    21

XXX explain comment format for documentation generation

    22

    23

    24

Coding

    25

~~~~~~

    26

- Don't forget 'var' before variable definition, and semi-colon (';') after **each** statement.

    27

- Check the firebug console for deprecation warnings

    28

    29

    30

API usage

    31

~~~~~~~~~

    32

- unless intended, use jQuery('container') rather than jqNode('container')

    33

    34

    35

See also

    36

~~~~~~~~

    37

http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml