Earlier quoted context omitted.
Who cares. It's IE which needs to catch up to the standards Mozilla and Google are implementing. It's not like Windows users will be left out in the dark, they can always install Firefox. Tell your users to use a real browser, or write a letter to Microsoft telling them to get with the times... Even the University I attend doesn't support IE with their web-apps. They support Firefox...
Unfortunately we have a lot of school administrators using our app with their Dept of Ed issued computers. The same DOE that actively encourages everyone to use IE and disallows software upgrades without IT help. Trust me, we try to get them to switch to Chrome/FF but it's an uphill battle.
Introducing TogetherJS
71–80 of 87 posts
Re: Introducing TogetherJS
#72I'm very excited to see so much enthusiasm for TogetherJS. We are currently building something similar and plan to release that next week. It has lots of similarities but we target a somewhat different market. Some of the differences, you do not need to write a single line of code and it will even work with advanced application that require sign in without sharing security tokens. We plan to release Surfly next week,…
Will this be open source, too?
Re: Introducing TogetherJS
#73This looks great but it seems they have no plans to support Internet Explorer ( https://togetherjs.com/docs/#browser-support ). That's a shame because most of our users who need this level of support all use IE :/
Speaking as the principal developer for TogetherJS: In the past we have opted not to work on IE support because we had limited resources, and because we wanted to focus on what we thought were the hard problems: how should the tool act, how do we communicate changes between browsers, how do we integrate with apps, etc. Supporting Internet Explorer was always something we knew we could do, it wasn't a hard problem, bu…
Re: Introducing TogetherJS
#74What worries me, and I realized this only after trying TogetherJS, is that Websockets don't require a special permission in browsers! So any website with JS enabled is now going to be able to do peer-to-peer? Could this be a can of worms, security-wise?
2. WebRTC allows P2P. Can't see how it's a security issue.
Re: Introducing TogetherJS
#75Is WebRTC better for real-time apps (drawing, games) than WebSockets?
Re: Introducing TogetherJS
#76Re: Introducing TogetherJS
#77This looks great but it seems they have no plans to support Internet Explorer ( https://togetherjs.com/docs/#browser-support ). That's a shame because most of our users who need this level of support all use IE :/
Yesterday, IE users weren't using TogetherJS, either, and I'm sure you weren't bothered by it at the time.
Re: Introducing TogetherJS
#78This looks great but it seems they have no plans to support Internet Explorer ( https://togetherjs.com/docs/#browser-support ). That's a shame because most of our users who need this level of support all use IE :/
You can check out GoInstant as well, which supports IE 8+ http://goinstant.com
Re: Introducing TogetherJS
#79This looks great but it seems they have no plans to support Internet Explorer ( https://togetherjs.com/docs/#browser-support ). That's a shame because most of our users who need this level of support all use IE :/
Well, maybe you should contact Microsoft and ask them to provide a port or provide similar functionality. Your users have, after all, paid Microsoft for the privilege of using IE.
Re: Introducing TogetherJS
#80Earlier quoted context omitted.
Well, maybe you should contact Microsoft and ask them to provide a port or provide similar functionality. Your users have, after all, paid Microsoft for the privilege of using IE.
Last time I checked IE was free.