Having the knowledge of LoopBack server-side javascript and strong-remoting conventions, I find the name ModelPrototype misleading.

 - The existing code uses "prototype" to mark functions that are member methods, i.e. must be invoked on an existing object. Example: `save()`.
 - In the client SDK code, we are using "prototype" for functions that are static, i.e. are invoked without a "this" object. Example: `find()/findById()`.

I have just realised that iOS client SDK uses the same naming convention and you are probably just following it.

@Schoonology @ritch @raymondfeng What's your opinion?

Considering what kind of methods we have on ModelPrototype now (`find`, `findAll`, `create`, etc.), I would suggest to use `ModelRepository` or even `Repository` name instead (see [Patterns of Enterprise Application Architecture](http://martinfowler.com/eaaCatalog/repository.html)). 

However since developers can attach arbitrary methods to this object, these alternatives may be better:
 - `ModelFactory`
 - `ModelClass` (and optionally rename `Model` to `ModelInstance` too)

I am also wondering how much space we have for client SDK's API changes, considering we have already released v1.0?