Currently can-connect connection options are stored in the top-most object in the connection prototype chain. This is somewhat unintuitive since options are subject to being hidden by properties on behaviors since they are lower on the prototype chain. Relatedly the options object would be a good place to store connection-specific overrides of behavior methods but this currently can't be done because the behavior will always be lower on the proto chain than the options.
Likely implemented as part of #304.
Currently can-connect connection options are stored in the top-most object in the connection prototype chain. This is somewhat unintuitive since options are subject to being hidden by properties on behaviors since they are lower on the prototype chain. Relatedly the options object would be a good place to store connection-specific overrides of behavior methods but this currently can't be done because the behavior will always be lower on the proto chain than the options.