628
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − [[Category:Feature Page Incomplete]] Line 20:
Line 19: − + Line 38:
Line 37: − User experienced is untouched.+
Features/Optional adhoc autoconnect (view source)
Revision as of 15:40, 20 April 2015
, 15:40, 20 April 2015no edit summary
<noinclude>
<noinclude>
[[Category:Feature|Optional Adhoc Autoconnect]]
[[Category:FeatureLanded|Optional Adhoc Autoconnect]]
</noinclude>
</noinclude>
''This proposal is based around the needs of the OLPC project in Australia, but reflects a common need (current or future) of other OLPC implementations as well.''
''This proposal is based around the needs of the OLPC project in Australia, but reflects a common need (current or future) of other OLPC implementations as well.''
'''The problem:''' Having hundreds or thousands of sugar clients creating or connecting to these adhoc networks by default is not necessary a desirable behavior, specially considering that only a few of these could actually be using collaboration.
'''The problem:''' Having hundreds or thousands of sugar clients creating or connecting to these adhoc networks by default is not necessary a desirable behavior, specially considering that only a few of these are actually using collaboration.
The proposed solution is to provide a system configuration so this behavior can become optional and not mandatory as it is now.
The proposed solution is to provide a system configuration so this behavior can become optional and not mandatory as it is now.
== User Experience ==
== User Experience ==
The new configuration will preserve the current behaviour by default, therefore the user experienced is untouched.