Recent Changes - Search:

Wiki

Documentation

Tutorials

Example Code

Documentation.FAQ History

Hide minor edits - Show changes to output

Changed lines 3-5 from:
-> '''Can I use MediaSense in my own project?'''
-> Yes, The MediaSense platform is open source and licensed under the LGPL license.
-> This means you can create your own applications (even commercial ones) using MediaSense.
to:
-> '''Can I use the SensibleThings platform in my own project?'''
-> Yes, the SensibleThings platform is open source and licensed under the LGPL license.
-> This means you can create your own applications (even commercial ones) using the platform.
Changed lines 8-9 from:
-> '''When will MediaSense be able to do...?'''
-> We have a roadmap for our own contributions and research, but we also have students and industry who contribute to the MediaSense platform.
to:
-> '''When will SensibleThings be able to do...?'''
-> We have a roadmap for our own contributions and research, but we also have students and industry who contribute to the SensibleThings platform.
Changed lines 12-13 from:
-> '''MediaSense does not work...'''
-> The most common problem when MediaSense does not work has to do with your own network connectivity, firewalls, network policies, etc.
to:
-> '''SensibleThings does not work...'''
-> The most common problem when SensibleThings does not work has to do with your own network connectivity, firewalls, network policies, etc.
Changed line 15 from:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can penetrate NAT using proxying but it is not a scalable approach.
to:
-> Avoid NAT traversal if possible, SensibleThings's peer-to-peer traffic can penetrate NAT using proxying but it is not a scalable approach.
Changed lines 14-16 from:
-> Therefore, make sure ALL your devices are connected to the same network. We strongly recommend to only use machines on the public Internet.
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT. Also, avoid operators and ISPs that block peer-to-peer traffic.
-> Changing to "Server" lookup instead of "Distributed" can help avoid some of the NAT based problems.
to:
-> Therefore, it is best if ALL your devices are connected to the same network. We strongly recommend to only use machines on the public Internet.
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can penetrate NAT using proxying but it is not a scalable approach.
-> Also, avoid operators and ISPs that block peer-to-peer traffic.
Changed line 16 from:
-> Changing to "Server" based lookup instead of "Distributed" can help avoid some of the NAT based problems.
to:
-> Changing to "Server" lookup instead of "Distributed" can help avoid some of the NAT based problems.
Changed lines 15-16 from:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT. Also, avoid operators and ISPs that block peer-to-peer traffic.
to:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT. Also, avoid operators and ISPs that block peer-to-peer traffic.
-> Changing to "Server" based lookup instead of "Distributed" can help avoid some of the NAT based problems
.
Changed lines 15-16 from:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT.
-> We have also noticed that some mobile operators block peer-to-peer traffic.
to:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT. Also, avoid operators and ISPs that block peer-to-peer traffic.
Changed lines 15-16 from:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT.
to:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT.
-> We have also noticed that some mobile operators block peer-to-peer traffic
.
Changed line 9 from:
-> We have a set roadmap for our own contributions and research, but we also have students and industry who contribute to the MediaSense platform.
to:
-> We have a roadmap for our own contributions and research, but we also have students and industry who contribute to the MediaSense platform.
Changed line 15 from:
-> Avoid NAT traversal, MediaSense peer-to-peer traffic can not penetrate NAT.
to:
-> Avoid NAT traversal, MediaSense's peer-to-peer traffic can not penetrate NAT.
Added lines 12-15:
-> '''MediaSense does not work...'''
-> The most common problem when MediaSense does not work has to do with your own network connectivity, firewalls, network policies, etc.
-> Therefore, make sure ALL your devices are connected to the same network. We strongly recommend to only use machines on the public Internet.
-> Avoid NAT traversal, MediaSense peer-to-peer traffic can not penetrate NAT.
Changed line 8 from:
-> '''When will MediaSense be able do do...?'''
to:
-> '''When will MediaSense be able to do...?'''
Added lines 7-11:

-> '''When will MediaSense be able do do...?'''
-> We have a set roadmap for our own contributions and research, but we also have students and industry who contribute to the MediaSense platform.
-> Otherwise you are free to build and contribute with the sought after functionality yourself. Please contact us for it to be included in the public releases.
Changed line 3 from:
-> * '''Can I use MediaSense in my own project?'''
to:
-> '''Can I use MediaSense in my own project?'''
Changed line 5 from:
-> This means you can create your own applications, even commercial ones, using MediaSense.
to:
-> This means you can create your own applications (even commercial ones) using MediaSense.
Changed line 4 from:
-> Yes, The MediaSense platform is open source and licensed under the LGPL licence.
to:
-> Yes, The MediaSense platform is open source and licensed under the LGPL license.
Changed line 6 from:
-> To Read more, see [[http://www.gnu.org/licenses/licenses.html | GNU Licenses]]
to:
-> For more information, see [[http://www.gnu.org/licenses/licenses.html | GNU Licenses]]
Added lines 1-6:
Here are answers for some Frequently Asked Questions

-> * '''Can I use MediaSense in my own project?'''
-> Yes, The MediaSense platform is open source and licensed under the LGPL licence.
-> This means you can create your own applications, even commercial ones, using MediaSense.
-> To Read more, see [[http://www.gnu.org/licenses/licenses.html | GNU Licenses]]
Edit - History - Print - Recent Changes - Search
Page last modified on July 29, 2013, at 01:11 PM