|
|
Previous Booth
Next Booth
Return to Search
Entrance
Showcase
GuestBook
Contact
|
 |
ROLLOUT PLANS
The infrastructure added for Jugtopics will aid other personalized
or secure web apps. To see this, view JugTopics as a prototype for
this tiered stack of web app and middleware modules:
Jason's design for web surveys lets them be declared in XML files.
Jugtopics reused Jason's excellent idea to publish David's results,
but repaid it with a new way to share user identities across web app
boundaries. The next steps should take the combination further, so
that new 1-to-1 survey apps become straightforward to define, post
and tally at need, with admin controls over who sees what.
Jugtopics modules get attributes of their user from session variables
in /projects, another web app. The next version of
this little trick lets it work securely over the Net, so that a
JUG visitor logging into /projects at once gains access to other
secure 1-to-1 web pages anywhere within a federation of other
web sites, manually registered in /projects.
Jugtopics voters register themselves in a singleton /project
class called UserBase, which provides for storage. How do we
link the UserBase class, and the rest of the User Registry, with
MySQL? I suggest that Craig finds the answer, by locally adjusting
the class logic without changing its current (simple) API. That way
JUG gets its own User Registry, independent from VTS.
Craig's new MySQL data base will let us model and find users, surveys,
meetings, etc. with relative ease. How we jointly manage, expand,
access, and share such information resources will add new dimensions
to the Projects we contemplate, and new ways to architect their
software. The UI code for Jugtopics login and registry still works
from a CSV file. Backing it instead with MySQL is a key next step
for MaineJug.
|
|
