[TIMOB-2953] iOS Feature Request: ImageView validatesSecureCertificate property

I'm hesitant to add such a functionality in, because it presents a slippery slope. Why would we stop at one HTTPClient feature? When you use a coverflow view, which allows for remote images as well, should this functionality also be allowed? How would you represent this; do you have one setting that applies to all images in the array, or can you specify per-image?

All of this gets even messier when you realize that the imageView isn't the one doing the actual connecting, and that it's possible that multiple imageViews could be wanting to load the same image, where one wants to load with ABC:true, the other with ABC:false.

There is already a problem where ImageView is being treated as a magical image handling, downloading, and manipulation utility, instead of what it really is: A view that shows an image. The much better behavior is that the end dev uses HTTPClient to download the file, and show that. That even has the advantage of taking up less memory.

That is true, but in my case I have a scrollable view loaded with image views and it had memory issues related with:
- http://developer.appcelerator.com/helpdesk/view/46321">http://developer.appcelerator.com/helpdesk/view/46321 Now the scrollable view filled with image views works like a charm but only if I put url to image property. In my case (at the moment) there is max 100 pics per scrollable view and only one scrollable view can be shown in my app. If I put binaries instead of url's to image property, when simulating picture slide show, the application after some time still crashes, but if I use url's it works forever :). I rewrote several times this application I'm working on for almost a year using first url's, then, after it stopped working with self-signed certificates, I used HTTPClient to fetch image base64, and then again using url's because of stability of my app.
Currently, I have a switch to switch between these approaches for future :).
But seriously, with url's it works excellent and I'm very happy with it, but at the current moment I gave up from SSL although I have everything ready for that in my app and on my picture server that serves the pics. And that is a feature I don't want to give up for next version if not for the initial, even if that means rewriting the whole app in objective C.

So I think that for one or some more pics it's a good approach to use HTTPClient to get the pics, but for more, from my experience it's not. For some reasons, that I don't know and you guys probably know why, when using url's the whole concept of scrollable view works much faster when scrolling left-right.
If my whole concept somewhere misses something please correct me.