List view
There have been several suggestions on how to make the TeleSign Java SDK more useful. Some of the changes we are planning would introduce backwards compatibility issues. Below I have outlined a few of the changes we would like to introduce as part of v1.0.0. Please provide any feedback regarding the proposed changes (items in no particular order). * Adhere to Java naming conventions and cleanup inconsistencies. * ex: public Verify(String customer_id, String secret_key, int connectTimeout, int readTimeout) * Easier way to maintain request parameters as appose to just overloading methods. Especially useful when new features are introduced and code hasn't been updated. * ex: Map<> parameter, Builder Pattern, others? * Better error handling, currently errors are captured and written to System.err. We should introduce proper TSError classes and not write them to System.err. * Better handling of response data. Its nice to have the actual field name described within a concrete class but it would also be useful to just return the raw data. This is especially true for products like PhoneID where new data nodes could be added to existing products. * Better unit testing. Today we have some unit test that aren't very useful and require that it runs against a live server. * Ensure we support http/s proxies. This might already be supported. * Update SDK to support missing products. * Review current dependency list and see if they are really needed. * Add support for Maven. * Deprecate Ant builds? * Add support for OSGi. * Proper javadocs. * Added User-Agent to http request so we can more easily track TS SDK based requests * Update GitHub documentation and have tech writer review.
No due date•13/13 issues closed