What else do you want from next release of VI Java API?
After we released VI Java 2.0 GA for about half year, it’s about time to plan for the next release. My current plan is to have a synchronized release with next major release of vSphere. Therefore the must-have feature is to support next vSphere.
On top of that, here are several things we most likely do as well:
Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.
- Support vSphere solution products like SRM, Lab Manager. Our SRM QA team has done investigation and came up with a prototype last summer. The Web Service engine needs to be modified a little for this requirement.
- Enhance caching framework. I still take the caching framework as experimental in 2.0, but many companies I know already used it in real projects. The magic side is you can get the properties faster than via normal retrieval.
Two possibilities are there with enhancement. First, open up the subscription for notifications. I used the Publisher-Subscriber pattern in the framework, and allowed only one subscriber which is the local cache instance in 2.0. This works perfect for caching purpose. To fully leverage the infrastructure already in place, we need to open up the interface for others to get notification.
The other possibility is to provide search capability to the local cache instance. It would just search whatever in the cache based on some criteria. Please let me know your use case that can leverage this local search over cache. Long term, I believe more search capabilities should be added to the server side so that you don’t need to pull everything locally in order to search what you want. But if you already have something locally in cache, a search utility could be handy.
- Per server HTTPS certificate handling. We currently have HTTPS support. But if you have multiple servers, you can either ignore certificate all or none. It’s better to have per server choice. Since you have our source code, you can modify it today. Some people already did in fact.
- More utilities that make development easier. I would call actions from the community: contribute your utility code that may benefit others; voice your wishes on the utilities you want. For the best quality, I have been pretty selective in adding new utilities. But if there are valid use cases, I am happy to add more utilities.
Please let me know your thoughts and add your wish list in the comments. I will summarize them into a final list for the community to vote.