ORTC is a W3C standard feature (http://ortc.org/) currently requesting for implementations.
For this specific demo we wanted to demo ORTC to ORTC communication so you need 2 browsers that support it. At this moment only Microsoft Edge on the latest insider flight does.
There are several initiatives to make the bridge between ORTC and WebRTC: simplewebrtc.com/audio.html is one that does that for audio.
[Disclaimer: I'm the PM and lead dev of this project]
Basically the rationale is that it is a beta website and we didn't had the time to do all the optimizations we want. More updates and sections should be coming in the next few weeks.
Give it a try again. We've done some changes on the server side so you should see IE and log into IE much faster. Just make sure to use the same email as the one you received the notification.
And, if you frequently use IE virtual machines, you can use the ievms[1] script to manage the downloads, expiration times, etc. Saves a ton of bandwidth and disk space over the modern.ie downloads, too (it uses the modern.ie images as base installs).
That's often but not always true: if you use VMWare on Linux or use an OS which is configured not to run arbitrary executables you can't use the self-extracting file. I certainly wouldn't say those are common problems or insurmountable but they're in the class of things which you simply don't need to worry about with ZIP.
I've always wondered if there's a story behind modern.ie using chunked .rars over e.g. non-chunked .zip.
What were the technical/human constraints that lead to that solution? Was the team agonising over conflicting goals? Or was it as simple as "Alice already knew it"/"Our tool chain already supported it"?
Hi acdha,
1. You can go to http://feedback.azure.com/forums/247748-azure-remoteapp and share your feedback with the Remote App team. They really want to make it as useful as possible and it is still on Preview so now is the moment to influence the team
3. Yes, we are working on it and should be fixed soon.
Regarding the older versions of IE, unfortunately we are running on top of Server 2012 so we are locked to IE11+. At this moment you can use the dev tools and change the compat mode and we are thinking about adding Enterprise Mode to the service so you can test on "IE8".
Are bugs related to Remote Desktop performance best reported against the client or Remote App? It doesn't appear to support bitblts so simply moving a window is extremely jerky and things like CSS transitions are basically a slideshow.
Enterprise Mode would be useful since that's getting a bit of traction as an alternative to staying mired in IE8.
There is no GPU acceleration. When running IE through RDP we default to software rendering and unfortunately there isn't anything we can do about that :(
Not even old-school acceleration like we used to have in the 90s? I thought RDP used to at least support things like "move this rectangle to a new position" for the performance win over things like VNC.
For this specific demo we wanted to demo ORTC to ORTC communication so you need 2 browsers that support it. At this moment only Microsoft Edge on the latest insider flight does.
There are several initiatives to make the bridge between ORTC and WebRTC: simplewebrtc.com/audio.html is one that does that for audio.