I am sure there are many, many app framework designs that all solve
various parts of the web application problem domain to varying degrees.
And cultures can clash that make it difficult for everyone to work on
one project. So good luck on your endeavor to make an app framework
that is simple and concise and still provides something useful to many
people.
A couple points: ECS is very well documented.
My interpretation and IANAL: The LGPL and GPL have similar viral
clauses, which is the most objectionable part of the licenses for those
that don't like them. The LGPL's virus is suppressed by the existence
of other implementations that could be used in place of the LGPL'd
software. This means an almost identical api/framework would have to
exist not just another piece of software that solves the same problem.
As nothing like this exists (are you implementing a oss version of api
that is present in a closed source product?), the license on your work
is viral. If this is the intention fine, there is obviously lots of
good GPL software out there. If it is not your intention please adopt a
BSD/ASL style license, many people find them appropriate for lower level
api's/frameworks.
I did take a cursory look at WebWorks but did not get to the point where
I understood its pull model. Further expansion on this topic would be
appreciated.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
