if they are accessing an HTML resource, the kid can have a cookie, or a
CGI hidden field that gets passed in the URL as they call the resource.
That would work like "logging in" into any webpage as we are used to do,
hopefully done only once, and then kept as a cookie field. That would
require no deep magic hacking.
I have become convinced that interaction with servers should be through
HTML, and hopefully someday an OS will have simply a browser, and
anything and everything will be run as a service in the server. That
would make it so much cheaper to maintain the OS, and probably make it
much faster and effective. For local (non-connected) use, the OS could
have an internal server, same thing - the GUI would be an HTML page.
this, of course, is for school /users/. Those who deserve better should
have a very solid Terminal, and binaries.
Anyway, even the local Community College I go to nowadays does every
administrative task on browsers. Still paying full licenses, of course!
On 12/02/2012 10:27 PM, Tony Anderson wrote:
Hi,
The Saint Jacob school has one laptop per child in grades 4, 5, and 6.
The teachers in the lower primary (K, grades 1, 2, and 3) want to use
them for selected lessons.
There needs to be a way for the work of each student who is sharing a
laptop to be kept separate. In particular, the school server knows the
class of the student who 'owns' the machine and provides access only
to those lessons.
I consider this requirement as less than One Laptop Per Child.
I propose the following:
Modify the XO menu (home screen) to add a 'new' tab. This tab can be
used to assign another nick. For example, there could be the student's
nick plus a nick for the family to keep family use separate from the
students. This tab would bring up the original login screen to allow
selection of a nick and colors.
Separate datastore folders would be set up in
/home/olpc/.sugar/default/datastore with a link to datastore for the
logged in user.
When the laptop connects with the schoolserver, it will identify both
the serial-number and nick for the laptop.
On the schoolserver, the /library/users/serial-number folder will have
folders for each user. The serial-number key pair would be used for
authorization and then backup would go to the correct folder (the
backup program would be aware of multiple users).
I would appreciate any suggestions for better ways to do this and for
anyone who sees something I have missed.
Tony
_______________________________________________
support-gang mailing list
[email protected]
http://lists.laptop.org/listinfo/support-gang
_______________________________________________
IAEP -- It's An Education Project (not a laptop project!)
[email protected]
http://lists.sugarlabs.org/listinfo/iaep
