Features/Optional adhoc autoconnect: Difference between revisions

Tch (talk | contribs)
Created page with "<noinclude> Optional Adhoc Autoconnect Category:Feature Page Incomplete </noinclude> == Summary == Add a new configuration to disable adhoc autoconn..."
 
Godiard (talk | contribs)
No edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
<noinclude>
<noinclude>
[[Category:Feature|Optional Adhoc Autoconnect]]
[[Category:FeatureLanded|Optional Adhoc Autoconnect]]
[[Category:Feature Page Incomplete]]
</noinclude>
</noinclude>


Line 20: Line 19:
''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 way a 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.


== Benefit to Sugar ==
== Benefit to Sugar ==


Make sure friendlier with the spectrum and save device battery.
Make Sugar friendlier with the spectrum and save device battery.


== Scope and implementation ==
== Scope and implementation ==
Line 38: Line 37:


== User Experience ==
== User Experience ==
User experienced is untouched.
The new configuration will preserve the current behaviour by default, therefore the user experienced is untouched.