Should we use "api" in the API package name ? I think we should not..
Currently we have org.wso2.carbon.user.api, org.wso2.carbon.regostry.api and possibly many more.. I think should avoid putting API in the package name - and it should be quite obvious.. For example, in Java - in JDBC API [1] - there in no API package name.. Also - the Java Collections API [2] - and JMS API [3] It has been an industry best practice to not to use the word "api" in package name.. I think we should follow that too ? [1]: http://docs.oracle.com/javase/7/docs/technotes/guides/jdbc/ [2]: http://docs.oracle.com/javase/7/docs/api/java/util/Collections.html [3]: http://docs.oracle.com/javaee/6/api/javax/jms/package-summary.html Thanks & Regards, Prabath Twitter : @prabath LinkedIn : http://www.linkedin.com/in/prabathsiriwardena Mobile : +94 71 809 6732 http://blog.facilelogin.com http://blog.api-security.org
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
