We've seen interest from multiple parties for Java library development.
I want to ensure that our toolkit Java resources are being use to
produce the best library we can.
I think it makes sense for Christian, Prasith, Kyle, and any other that
are interested in *developing* and *supporting* Java to engage in
discussion here on how to move forward with the Java toolkit(s).
I have seen discussion on the merits of code generation, but I don't
think there is any disagreement that if we are using code generation, we
should use the Common machine descriptions. Is there any other
technical justification to have two separate java toolkits?
If there is not sufficient technical justification, what is involved in
merging this new effort with the existing one?
Regards,
Paul
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
