{"push_id":760944641,"size":1,"distinct_size":1,"ref":"refs/heads/engines","head":"c58a706e3eb395c534e925b05b600bc851c5ac41","before":"50fcf30f88e3ee2b72570f082d2d698b52331246","commits":[{"sha":"c58a706e3eb395c534e925b05b600bc851c5ac41","author":{"email":"2591e5f46f28d303f9dc027d475a5c60d8dea17a@cerebris.com","name":"Dan Gebhardt"},"message":"Update Engines RFC with more detailed, incremental alternative.\n\nThis proposal discusses the benefits of developing and delivering engines in\nmultiple phases.\n\nIt's proposed that we start with an initial release that provides the benefits\nof distributed development, integrated routing, and clean boundaries between\nengines and their parents.\n\nSubsequent releases could include features such as lazy loading and namespaced\naccess to engine resources from their parents.","distinct":true,"url":"https://api.github.com/repos/dgeb/rfcs/commits/c58a706e3eb395c534e925b05b600bc851c5ac41"}]}