05-05-2010 10:51 AM
The Omission of caching (at least image caching) in the V5 browser field and the lack of control over where the V5 content comes from (the Controller class is really inadequate to use for caching) is causing me to "rethink" using the V5 browser over the V4 browser APIs put in since 4.5.
Add to that I need 2 different implementations if I use V5 (to handle V5 and pre-V5) and it means testing/supporting both.
So - somebody tell me why I should not simply use the pre-V5 browser mechanisms and make that work versus supporting 2 implmentations and having to do my own caching (why the heck didn't RIM simply add this - it's a must have!!).
Will the pre-V5 browser stuff be deprecated? Is there something I can do with V5 that can't be done with pre-V5? someone enlighten me....