observing / fossa Goto Github PK

...

Extended Fossa Models and Collections should get some handy methods to set/get additional stuff before initialization of the constructor.

var Account = fossa.Collection.extend({
    name: 'accounts'
  , database: config.get('mongo').database
});

Account.virtual('sub').get(function () { ... })

Methods that come to mind

• validate
• virtual
• hook
• options

Currently Fossa stores any database change in the client. This functionality will mostly be used by our Conductor to store Session data. However, this could potentially lead to issues. What happens if multiple instances are writing at once

The idea behind storing the instance is so that Fossa.collection will switch to the collection inside the last database provided to Fossa. Making sure that all writes (and potentially reads) use the same client.

Another approach is only store the initial connection to . The question is then does it blow up the connection pool and create new connections for each instance returned with the callback. Logic dictates otherwise.

In any case, switching between both solutions is easy, as we would not call fossa,collection but the client.collection returned from the callback of fossa,connect