This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
content:servalmesh:releases:version_0_90 [01/05/2013 22:50] Andrew Bettison content:servalmesh:releases:version_0_09 renamed to content:servalmesh:releases:version_0_90 |
content:servalmesh:releases:version_0_90 [27/05/2013 21:29] Andrew Bettison [Milestones] link to Security Framework tech roadmap page |
||
---|---|---|---|
Line 20: | Line 20: | ||
* Revamped user interface to give a more consistent feel to the application | * Revamped user interface to give a more consistent feel to the application | ||
* Vastly improved stability | * Vastly improved stability | ||
- | * All new security architecture based on Elliptic Curve Cryptography, with a PIN-lockable | + | * All new [[: |
- | * New mesh network | + | * New [[: |
- | * Improved file distribution ([[content:technologies: | + | * Improved file distribution ([[:content:tech: |
- | * New voice over mesh protocol to replace SIP and provide encryption ([[content:technologies:vomp|VoMP]]) | + | * New [[:content:tech: |
- | * New mesh text messaging service ([[content:technologies:meshms|MeshMS]]) | + | * New mesh text messaging service ([[:content:tech:MeshMS|MeshMS]]) |
* Audio latency and quality suitable for demonstration | * Audio latency and quality suitable for demonstration | ||
- | * All software features will work on Wi-Fi networks if Ad-Hoc mode is not available | + | * All software features will work on Wi-Fi networks |
- | * Integration with Android contact book to store names, numbers and public keys | + | * Integration with Android contact book to store names, |
==== Known Issues ==== | ==== Known Issues ==== | ||
- | * [[content:technologies: | + | * [[:content:tech: |
- | * [[content:technologies: | + | * [[:content:tech: |
- | * [[content:technologies:meshms|MeshMS]] message bundles grow without limit | + | * [[:content:tech:MeshMS|MeshMS]] message bundles grow without limit |
* Issues of scalability have not been addressed | * Issues of scalability have not been addressed | ||
* Multi-hop communications have not been thoroughly tested | * Multi-hop communications have not been thoroughly tested |