|
|
|
 |
Java & Web Services We have a policy of writing applications for distribution to customers in Java. We also expose all of the configuration functions available in those applications as APIs and provide web services on top.
Elephantastic
Depends on what your goal is. If you are selling it as an application and don't expect people to customize it and build programs on top of your application, then it's a bad idea. Because they will, then they'll want to resell your application with their own, and then there could be a legal problem with that. If you do intend for them to build applications on top, perhaps the better idea would be to provide the application, and then provide (as an additional fee that only those customers that desire the capapbility pay for instead of all users) an SDK for your users. This will also possible clear up licensing issues for resale of your product, or at a minimum force you to think about them.
Elephant
Well it certainly is... brief.
Wunderkind
|
