Jim Marino wrote:
On Feb 22, 2007, at 4:40 AM, Rick Rineholt wrote:
I didn't see any mention what bindings are supported or have been
tested with this kernel release. In past we had several web services,
RMI all validating that the kernel and the SPIs. We also had several
implementation supported Java script, Ruby. It was my experience
that these really fleshed out a lot of issues and gave a lot of
confidences the kernel was working and could be used to build upon by
people wanted to build extensions.
That's one of the goals of having the kernel release, to get feedback
and validation on the SPI :-) Also, one of the goals of modularity as
I understand it was to enable releases early and often, with kernel
coming out before extensions. Otherwise, we will wind up in the
unworkable situation we did with the past two milestones releases.
In any event, the SPI for bindings has not significantly changed from
M2. I suspect they will somewhat when we introduce full support for
federation, put IMO it is important we get something out now to
validate where we are.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
If I start taking this kernel release and find issues what will be the
plan of action? Wait for the next release ? Goto the next SNAPSHOT
published driver?
I think a release of something should signify the community confidence
in what is being released. My experience has been in past releases it
wasn't till we had major integration of binding extensions, alternative
component implementations and some reasonably more that hello world
scenarios driving the kernel that I felt confident it was worth
releasing. Curious, how others feel about that ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
