Alternatively, we might consider something along the theme of "River
Delta" where a river meets the ocean.
Before a River opens to the wider world, it goes through the Delta.
Also, the test results represent a kind of a "delta" between what an
implementation is and what it needs to be.
I would have also suggested "confluence", where one river meets another,
but that's already taken. I suppose there might be confusion over
"delta" as well, but I think it's more manageable because it's not an
actual product name.
Just another suggestion for where things could go, to make up for my
previous contribution. :-)
jamesG
On 11/22/2010 10:52 AM, Gregg Wonderly wrote:
Just to clarify what I was trying to suggest... With the name River,
compatibility gates would be like Dams, stopping incompatibility from
getting through. If there is a Dam name, fun and clever to use, that
would be cool. If there are other names which are great, than that's
cool too.
Just trying to keep things "fun"!
Gregg Wonderly
On 11/18/2010 10:40 AM, James Grahn wrote:
Totality Of River Testing for Undoubted Rigorous Establishment of
Riverness
TORTURER
"Does my River implementation pass muster?"
"We'll let you know as soon as we run it through the TORTURER."
jamesG
On 11/18/2010 10:46 AM, Benson Margulies wrote:
Truly Open River Conformance Test Unlike Oracles Java TCK
TORCTUOJ
On Thu, Nov 18, 2010 at 10:36 AM, Dennis
Reedy<dennis.re...@gmail.com> wrote:
Can anyone think of name for the Jini TCK?
I'd suggest the name of a river Dam somewhere in the world. Any
suggestions of fun and non-controversial names? For example,
Hoover, is probably not good because eventually people would just
say "that sucks" -:)
Gregg Wonderly
Well, we could name it Chastise, after the Dam Busters from WW2.
Chastise also means to scold severely, which is what one would do
to someone who didn't honour the Jini Discovery and Join Protocol.
River Compatibility Kit or RiCK?
