I'd like to avoid the extra transaction when loading this code in the container, so I was thinking putting this all in a feature with the LICENSE and making it come down in the container core code so that we can use it everywhere. Over time I think it will really help us clean up some of our apis with callbacks being passed everywhere.
From: "Franklin, Matthew B." <[email protected]> To: "[email protected]" <[email protected]>, Date: 06/07/2012 03:04 PM Subject: Re: I'd like to include source from this project in shindig (js promises) On 6/6/12 1:43 PM, "Dan Dumont" <[email protected]> wrote: >https://github.com/kriskowal/q >I think this will make coding async operations in shindig MUCH easier to >do, read, review, troubleshoot , etc... >I'd like to target some spec changes (for 3.0 or later) as well to >specify >that some arguments to apis will take or return promises explicitly... >anyway... > >Can someone assist me with going through the steps necessary to satisfy >the legal requirements for this project in Apache? This is the MIT/X11 license and is suitable for inclusion per http://www.apache.org/legal/resolved.html. However, is there a need to include the source? Could we find a way to pull down the js at runtime or build-time to simplify things? Of course, if it is pulled down at build time, then we still need to put correctly put the LICENSE & NOTICE entries in the binary artifacts; but it would mean not having to manage code directly in Shindig's repository. -Matt
