This is a quick proposal for building out Jetspeed's WAP support.
The goals are to allow users to logon to Jetspeed via uplevel clients
(Netscape, Mozilla, etc) and also support WAP clients.
Some Portlets will never support WAP. That is fine. Jetspeed will
still play nice. Some Portlets however will support this fine.
CocoonPortlet and RSSPortlet will do great.
The only difference I want between Cocoon and Jetspeed in this is that
Cocoon will handle the multiple types and Jetspeed piece everything
together. The other issue is that any Portlet doesn't necessarily have
to use Cocoon or even XML, it could use ECS if it wanted. Choice is
good :)
Introspection support needs to be worked into Portlets. We should use a
db of HTTP_USER_AGENTS to determine client capabilities. The
introspection can then only provide data that the client can handle.
This concept maps to Cocoon media types very well.
MimeType[] getMimeTypes()
Could allow introspection from the Jetspeed engine into the Portlet to
find the types of content it supports.
It would be nice to have some basic types:
XMLType would be text/xml | text/xhtml | etc but would also return the
namespace for the document.
HTMLType would return the revision of HTML this supports or the client
it is targeting.
I honestly don't expect this to get too advanced. Right now I only want
the introspection for WAP support. We can let Cocoon handle really fine
level content control (IE vs Netscape).
Jetspeed will also need to have a getMimeTypes() on PortletControllers
and PortletControls. I a client connect to Jetspeed from their Cell
phone I want to point to WAPPortletController which will just give back
a deck of Portlets that support WAP.
The other issue is how the Portal/Jetspeed is customized. The
customizer that is in CVS has been written in Cocoon/XSP so we can have
a WAP media target here. It would probably create a file
(/users/burton/default.wap.psml) that would be the version of the same
Portal but with WAP support. Since some content might not support both
WAP and HTML it is possible that content wouldn't be able to run in both
environments.
Thoughts? I want to implement this in the 1.2/1.3 area. Honestly it
isn't that far of a stretch to get it to work. Maybe a day of
dedication.
Kevin
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
