added the ability to specify storeName as an attribute on a collection or model to give it a name other than it's url
Ensure models in the dirty list exist before saving

This mitigates concurrency issues noted in #62 until #35 is resolved, which should fix this problem.
Revert syncDirtyAndDestroyed ignoring local/remote options from #65

This was ineffective for its purpose and caused local/remote to be
ignored at uninteded times, as in #62, #70.

Revert 25b890f8eb7807ed93052d0044f76150ae64f794 "syncDirty disregards local/remote options too".
Revert 48fb69555d2207d64d4f68d765d6602d294b3af1 "syncDirtyAndDestroyed is not affected by local/remote options"

Conflicts:
	backbone.dualstorage.amd.js
	backbone.dualstorage.coffee
	backbone.dualstorage.js
	spec/backbone.dualstorage.js
Merge pull request #18 from ajhodges/master

Allow specifying the storeName to override the default url-based storeName.

Closes #61.

Conflicts:
	backbone.dualstorage.coffee
	backbone.dualstorage.js
Document storeName in the README and CHANGES
Guard against JSON.parse(null) and simply return null
Build javascript
Merge branch 'avoid-json-parsing-of-null'
Dirty and destroyed should also check storeName items
Merge pull request #72 from jeroencoumans/master

Dirty and destroyed should also check storeName items
Test syncDirty with new (not synced) records with temporary ids
Refactor where()[0] to findWhere()
Use model.urlRoot as the storeName, when available, before model.url

This fixes #80 where models with the same `urlRoot`
that are intended to be part of the same collection end up in different stor
when the collection attribute is not set on the model.

**Existing apps that rely on this incorrect behavior may break.**

If your app expects models with the same `urlRoot` and differing `url`s to
be in different stores locally, use the following workaround in your model:

      storeName: function() { return this.url() }
Bring changelog up to date
Compile javascript
Align assignments where it shows commonality on the right hand side
Add specs for dualsync storeName selection
Comment cleanup

GUIDs will be unique with more certainty than the Earth expliding in the next second. Why introduce doubt here?
Avoid using clone to avoid issues with backbone-relational and others

See #75
Ensure the id on modelUpdatedwithResponse gets set properly

Set the idAttribute before the attributes so it can set the right attribute to be the id.