Features/Optional adhoc autoconnect: Difference between revisions
No edit summary |
|||
| Line 20: | Line 20: | ||
''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 | '''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. | ||