On 10.5.16 5:39 , Ian Boston wrote:
I don't have a perfect handle on the issue he is trying to address or what would be an acceptable solution, but I suspect the only solution that is not vulnerable by design will a solution that abstracts all the required functionality behind an Oak API (ie no S3Object, File object or anything that could leak) and then provide all the required functionality with an acceptable level of performance in the implementation. That is doable, but a lot more work.
I doubt this. It is a lot more *upfront work* vs. never ending fire fighting in production systems.
Michael
