---------- Forwarded message ----------
Date: Fri, 26 Jan 2001 16:59:35 -0500
From: Geoffrey Fox <fox@csit.fsu.edu>
To: Sung-Hoon Ko <shko@csit.fsu.edu>, Ahmet Uyar <auyar@csit.fsu.edu>
Cc: John Yin <johnyin@anabas.com>
Subject: Anabas Stuff
Here is Anabas Infrastructure in a jar file
There is also Overview of Sharedlets and
Shared Display format
As this is proprietary, pease keep track of where it is!
Please contact John Yin if problems
John: I chopped my team into groups and Sung-Hoon (who did JMS work)
and Ahmet (who has been working on HearMe) will be leading
"infrastructure"
It
is recommended that each sharedlet, when creating streams to communicate
between views and session logic, to use as the stream name a derivative of its
MIME Type. For example:
x-sharedlet-whiteboard/private.
The
recording/playback service provided by the framework will recording all events
sent to the sharedlet and play it back at a later time. In order to better support
recording/playback, a sharedlet’s communication mechanism should have the
following characteristics:
(2) If the sharedlet contains non-deterministic elements, the result of the non-deterministic action should be broadcast as an event and the state updated accordingingly.
Each capability is a raw feature that the sharedlet will ever want to access
control. In the whiteboard sharedlet
example, the ability “draw” and write “text” are two capabilities
·
Roles
A role is a list of capabilities that are enabled. This definition is used to define the initial environment for a
user when the user’s virtual classroom or collaborative application
launches. This parameter is normally
set by the management framework via some parameter to the sharedlet framework.
A role also has a view definition associated to restrict what SharedletView’s
are available to what role.
· Moderatable Elements
A moderatable element is a convenient group of a set of
capabilities that a moderator or host can change during the meeting or
collaborative session. This list of
elements allow the framework to present a user understandable set of moderation
capabilities.
getRoleInfos();
getCapabilities();
All
moderation information are managed by the CapabilitesManager service within the
sharedlet framework. The capabilities
manager setups initial capabilities from the role definition for the invocation
and provide API’s that allow sharedlets to toggle moderatable elements on other
user’s instance of capabilities managers.
//
Define the list of all capabilities this whiteboard supports
setCapabilities(“draw,text,annotate”);
// Define the presenter role
setRole(“Presenter”,”draw,text,annotate”,”Control
Panel,Whiteboard Canvas”);
//
Define the co-presenter role
setRole(“Co-Presenter”,”annotate”,”Control
Panel,Whiteboard Canvas”);
//
Define the participant role
setRole(“Participant”,””,”Whiteboard
Canvas”);
//
Define a single moderatable element that a moderator or host can change.
setModeratableElement(“Present”,”draw,text,annotate”);
}
}
(1) Initialize the Sharedlet Session Logic server
(2) Launch the client side sharedlet framework UI with:
a. A defined set of sharedlets to run
b. 1 role for each sharedlet to run
c. The unique meeting context so the framework can set the correct context.
d. The location of the event bus server
(3) The sharedlet framework UI setups the sharedlet environment by:
a. Setting up the sharedlet context using the meeting id
b. Bind the appropriate session parameters in the context under session_param/
c. Create and intialize the sharedlet services under services/
d. The sharedlet manager service will instantiate the appropriate sharedlet info files
e. The layout
service will instantiate the views and the sharedlet themselves and render the
UI
|