I have not had a chance to play with these at all but from what I’ve read I agree that this is mainly designed for web applications, and the primary thing MS is thinking of when they build this are the big cloud providers out there who have to worry about tenant isolation at a far greater level than most companies. I’m not saying it won’t have other uses, but that’s what I see the main use being. I could see an argument for things like Citrix and RDS as well but I’m guessing that will come later. And just as to VDI, my own personal view, its a nightmare because we’re letting it be one, I think with the right attention it could be solved with a reasonable amount of effort. -----Original Message----- From: Blind-sysadmins <blind-sysadmins-bounces@lists.hodgsonfamily.org> on behalf of Katherine Moss <kmoss@winterhillsolutions.com> Reply-To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Date: Friday, April 8, 2016 at 10:09 AM To: "blind-sysadmins@lists.hodgsonfamily.org" <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] speculating on Hyper-V containers and accessibility
Hi,
Hopefully, considering Microsoft's new fantastic stance on the subject of accessibility, this new marvelous technology will be taken into account. I'd think it would work, because the application deployed in the container would more than likely be web applications. At the current moment, I've got all web sites on my IIS server deployed on one server, though I eventually want to make each site run under its own container to achieve even greater isolation. Do you folks see any potential issues with accessibility with screen readers? You think it's going to invoke the same nightmare that VDI does?
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins