On Mar 27, 2010, at 1024PM, Shay Hassidim wrote: > > > Contributing the specific code we have created to enhance the Jini > components would involve submitting also our proprietary communication > protocol technology and other components that provide us uniqueness when > competing with other products on the market. When having such a > competitive environment in a very hot market, I'm not sure it makes > sense to do so.
You are right, providing the source for your proprietary communication protocol does not make sense. But I am confused as to how your wire protocol and reggie internals intersect. Your wire protocol is how clients talk to the space, not how reggie scales right? I should be able to use your modified reggie by using 'stock' River components right? Or are you locked into using the GigaSpaces platform? Perhaps you could summarize the issue(s) you addressed with reggie internals? Would that work for you?
