This is a little bit related to the WAP issue brought up and it is also
related to my real-life needs.
IMO, all portals essentially consist of "services": news, email,
calendar, contacts, etc. So, I propose to include the notion of services
into jetspeed (stored in PSML?): andministrator can assign different
portlets to different services. It also makes easier for the user to
choose among the portlets, helps to navigate when customizing their
pages.
The vision is (and our company is already working on something similar):
The basic services offered by jetspeed are authentication (well,
actually inherited from Turbine) and folder-like system for holding user
data (something like MS Outlook).
A folder can contain whatever items, but all items are inherited from
one base item that has most common properties (like permissions, etc.)
Each service has usually one folder (but could have more): tasks,
calendar (actually appointment items, but user sees calendar) have one
folder. On the other hand, email service has more than one folder:
inbox, outbox, sent items, etc.
PSML could contain information about all the services available on the
site. All the services are pluggable in the sense, that you can plug out
all the services from the portal and it would still work (you can log
on, but there is no content). Also, you can add services later on to the
portal.
All services have some basic configuration (that could also be stored in
PSML?) and then there is also user-specific configuration for each
service, also in PSML or in a table in a database.
Initially, when user signs up for an account, he is asked only the basic
information. As the user discovers step-by-step the services available
in the portal, he can sign up for them and configure these as he
proceeds. No need to fill in long forms at once.
How does all this apply to WAP? Well, when the user accesses the site
with his WAP device, he is presented a menu of services that he has
enabled, and then a menu of actions/portlets under these services. On
the website, he is also able to customize the menus that will be
presented to him on his mobile.
This concept of services would bring some order into the potential mess
of different portlets.
OK, I hope all this made some sense...
Neeme
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
