[Server-devel] [XSCE] The concept of "pushing" content to clients

[James Cameron]

There seems to be two main ideas here;

- remote control of a device in a multi-device scenario,

- the commanded store and forward of content.

The former is a surprising one to consider in the context of a one
device per child project.  Which device would be the remote control
for which other device?  Yes, it's notable, but so is possession of
more than one device.  If you mean remote control by a device in the
possession of another, that way seems risky.

The latter might be satisfied with a mail server configured to operate
without always-on internet service.  It might be wrapped with a web
mail instance, and local mailing lists for class or interest groups.
Content would be cached by the server until the mail is deleted.

Device side support for local caching could use a mail client that
exposes specific attachment types as Journal content entries.

The automatic conversion of specific web pages, as in your NYT
example, really only works with content that is self-contained.  Once
a link sends a learner off the page, we're back to square one.

(Consider augmenting the Wikipedia activity on Sugar, to provide links
to pages that aren't present, which places the download requests in a
queue for next connectivity event.)

-- 
James Cameron
http://quozl.linux.org.au/