On 21/03/2011 11:15, Michael Aram wrote:
* Treat the Java connector framework as part of the core *
As far as I know, the connector frameworks - including the reference
implementation - are considered to be provided by the community. Of
course, this makes sense for an open source project.However, as the
connector frameworks should serve as the starting point for new
developers / Wookie integrators, I would suggest to treat *the one*
reference implementation as "being part of Wookie core", which would
mean that it gets polished upon releases, would stay up to date with
the REST API etc...
I'm not sure what you are proposing here. The connector framework *is*
part of core, it's in trunk [1]. It doesn't make any sense to move it
into the widget server source folder since it is not part of the widget
server. Where are you suggesting we put it?
I also don't understand what you mean by "the one".
If you are suggesting that we define an "official reference
implementation" that is considered the "most complete" of all the
connectors then maybe you have a point. But which is the most mature?
For me it is the Java one as that's the one I work, but for others it
might be the PHP one or the Ruby one.
Perhaps you are suggesting we have a complete implementation of a
connector within Wookie to demonstrate how to implement a real connector
rather than provide templates for connectors as we currently do. This
makes sense too, but which application will we build it for?
It can't be the Drupal or Moodle conenctors as they both have to be GPL
licensed (and thus need to be maintained outside the ASF). It could be
the Simal one, but then Simal is niche product that very few people care
about so it's not a very useful reference implementation since it deals
with local Simal issues.
We could implement the connector within the wookie server and use that
on our widget testing pages, but that would require us to build a full
blown container within Wookie and I feel that's out of scope for the
project (others may disagree and I'm sure we would welcome patches).
I would suggest the right thing to do is work with the new Apache Rave
(incubating) project to provide a reference implementation there with
clear linking and documentation from our site to demonstrate how it is
built.
Sorry if I've misunderstood your point.
Ross
[1] https://svn.apache.org/repos/asf/incubator/wookie/trunk/connector/
