On 8/29/05, Massimo Foti <[EMAIL PROTECTED]> wrote: > Ryan, I like the idea and I quite share the vision behind what you are > trying to do. I hope you will keep driving the project forward.
Thanks massimo, I appreciate that! > After looking into COAL I have two comments: > > - It's not clear under which license you distribute the code. When you just > say "code copywright respective authors" it basically means I am not allowed > to use it on any project without permission from the authors (apart from > personal use/learning). It's nothing more than the default copywright that > apply to any content on the web. That's, at least, under italian laws. > Being more explicit about license issues would be useful forusers and > potential contributors. You are right, and that is something I hope to address soon. I dont know anything when it comes to licenses and so I hope to get some advice on that and update that part soon. Basically what I assume is that the COAL framework itself will be a very open license, you can basically do what you want with it, but we may have to have individual licenses for each of the components. Again, I encourage all services or components submitted to COAL to be open and open source, but they do not have to be, and you could potentially even offer services for sale to plug into COAL. I just need to get some help with that. > - At first glance it seems to me using COAL on a shared server could be > problematic. Naming/versions clashes among CFCs under shared boxes can be > nasty. I am not sure if you ever considered the issue. Well, it could be problematic yes, but all you would really have to do is to create a mapping of a different name. Also, unless you are putting custom or proprietary components into COAL for your own use, and as long as the services are design correctly, it shouldn't be a problem in a shared environment because all instance data should be set when the objects are instantiated, or they should be real services. So unless there was proprietary or some sort of specific logic or data in a component, it really shouldnt matter in theory if it is in a shared environment. But again, if there was a problem, you could just make a coal2 mapping instead and use it. the coal mapping is just a suggestion. > Keep up the good work > > ---------------------------- > Massimo Foti > Tools for ColdFusion and Dreamweaver developers: > http://www.massimocorner.com > ---------------------------- Thank you! I hope to! > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:216652 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
