On 14-12-10 17:24, Mike McGrady wrote:
I probably do not need to say that this is a very significant change and should
be justified by the most dire need.
I'm not really sure that this needs justification. I would be perfectly
happy for an improved spaces implementation to live alongside the old in
org.apache.river.spaces
Gr. Sim
On 12/14/2010 11:07 AM, Patricia Shanahan wrote:
Who controls the JavaSpace API specification? Is it something we can
change, as part of River, or do we just have an implementation?
Should we be considering designing RiverSpaces, similar to JavaSpaces
but with an updated API, including generics, more use of collections,
and better naming?
I think we should be free to change the specifications. RiverSpaces would be a
good thing, to signal deviation from the original specs.
Apache River Spaces would probably be the official name, for trademarks sake.
But in order to be sure, we should take this up with legal-disc...@.
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
