Backbone View Save (best practice)
===

If I have a class A that contains some properties a, b, and c, would it be ok it have a save method that is responsible for saving these attributes to the db. 

class A extends Backbone.View
  ...
  save: ->
    @model.set
      a : someVal
      b : someVal
      c : someVal
      

This seems like the most logical way to set it up, but would like to hear some suggestions on how you guys are doing it. Thanks!