Functions of SAIL and candidate technologies on which to build them.
Each proposed technology choice should explain how it addresses each of the necessary features of the category.
Setup
Mechanism for initial setup on a computer. Minimum interactions to start using.
User Data Synchronization
Collecting data generated by user.
Making accessible from anywhere.
Handling concurrent modification of shared data.
Untrusted local storage
Software Component Distribution
Software components are the Java classes and libraries that the content employs.
Packaging
Naming
Versioning
Transport
Storage
Shared libraries
Untrusted local storage
A page detailing software and content distribution procedures.
Pedagogical Content Distribution
Content is what authors produce and distribute to learners.
Packaging
Naming
Versioning
Transport
Storage
Untrusted local storage
See the Software Component Distribution page. The same technologies can be used for both of
these sections.
Security
Permissions
Roles
Storage
Encryption
Directory services (linking in with existing)
Discovery
Finding other running processes on the network.
Part of the core services of J2EE, applications have the ability to use components and data sources scattered on the network, independent of their physical location. The J2EE container services take care of the mechanisms for lookup and gathering of these components and data sources. All the application is concerned about is how to use these resources once they have been acquired.
Technologies used: JNDI, LDAP,..
The JNDI API is the standard API for naming and directory access. The JNDI API
has two parts: an application-level interface used by the application components to
access naming and directory services and a service provider interface to attach a
provider of a naming and directory service.
EJB containers can be clustered to share a single JNDI tree that searches for components throughout the network with knowing location specifics. This can be used for finding servers, users and components.
Servers
Learners
Software Components
Peer Communication
Messages and data sent between client machines.
Sharable artifacts
Latency
Interoperability
Have to ability to interop with components that are not SAIL or work on standard protocols.
See attached picture

Comments (3)
Mar 25, 2004
Scott Cytacki says:
I would vote to split this page up. With one page for each main section. But kee...I would vote to split this page up. With one page for each main section. But keep the description of the section on this page. If we want to get fancy we can use the [ include: notation so the description of each section is shared by both pages.
Mar 25, 2004
Turadg Aleahmad says:
Good idea, Scott. I say go for it.Good idea, Scott. I say go for it.
Mar 25, 2004
Scott Cytacki says:
What is the "naming" feature listed in the distribution section?What is the "naming" feature listed in the distribution section?