Re : How do I do the equivalent of compute.on/compute.off while using can.Map.define?

Ok, while that is pretty useful, that only applies to findAll, not findOne, and doesn't solve the issue of binding to changes, such as the can.route query or page attribute. Right now I'm wondering the proper way to hookup bindings.