538 karma · joined April 15, 2009
I'm interested in what a model layer would look like using protorpc. One idea is to take a similar path of abstraction as the underlying appengine datastore api does: use protocol buffers to express an "entity". So you might have:
{
entity_type: 'Book',
entity_fields: [
{
field_type: int,
field_name: 'title',
required: true
}
]
}
This would be a proto definition called, "Entity". From here you could build procedure calls that send entities for doing common routines, such as updates, or deletes. If you can make a structure like this work, you can build an api with javascript which hides the protobufs from you all together.. When you call Model.get('Book').create({title: 'My book'}), it constructs the Entity protobuf and calls the remote call for creating a new entity.Just an idea! Also - protorpc is in fresh development, so it's a good idea to join the discussion group and make suggestions: https://groups.google.com/forum/#!forum/google-protorpc-disc...
I've been using the library for 2 or 3 years now, and I am always surprised to see it has such a small community.
function bind(fn, selfObj) {
return function() {
return fn.apply(selfObj || window);
};
}
callback = bind(function(){ alert(this.hello); }, this);This somewhat hints to me that Apple will come out with a framework that allows more modular includes or compiles similar to closures system. This is somewhat a hit to jQuery's "all-in-one" setup.