2008/6/19 Aidan Skinner <[EMAIL PROTECTED]>: > I think this is a really bad idea, and I'm quite strongly opposed to > it.I think we should be releasing everything, but clearly documenting > what doesn't and doesn't work and why, and making sure that stuff that > doesn't work doesn't work in a humane, clear manner. Possibly with > comedy unhappy Simpsons error messages.
OK, if you want to release everything you have to be able to document to users why the C++ client doesn't talkt to the Java broker (or whatever combinations don't work). What is the advantage to our users of releasing everything? If we ignore resource constraints for a moment, would you want M3 to interoperate between all languages? What are the reasons a user would want to use an M3 java broker? RG
