There are several ways to set your code. Creating an ATM and distributing it, which might be the easiest, as other developers just have to turn on your bank. However, if you are talking about โanyโ access to your code, a web service may make more sense, since you can provide access to data without providing all the necessary code. You indicate that you provide access to your getters - if you just create a class with getters, other developers can use them, but how will they be populated? If your application is self-sufficient, it receives the necessary data and provides getters that should work, but if you are talking about providing access to data from your running application, the web service makes more sense, since your application can retrieve data and provide access using publicly available methods.
Most likely, you want to create interfaces so that developers can code the interface, and you can change the internal work without affecting them. Any API that will be used by others should also be documented.
Tai Squared Aug 31 '10 at 19:51 2010-08-31 19:51
source share