OK.. I am getting back in the groove. 2/3 of the way done my move :) Anyway. I have been doing a lot of thinking lately regarding XML and Jetspeed. There is an issue of how will Jetspeed handle dynamic content. I believe Landahl just talked about this. Initially I wanted Jetspeed to have a 'discussion' XML production mechanism. This way you could 'discuss' any Portlet within Jetspeed. RSS has me thinking in another direction... mainly down the road of using Jetspeed Content Mangement and an RSS threading mechanism. Check this out: http://www.oreillynet.com/~rael/data/xml/rss/modular/demo/ Pay attention to the threading mechanism. If we use JCM (JCM -> RSS) to produce content within Jetspeed we can have a full content building mechanism within Jetspeed. :) Basically it would work like this: - RSS Portlet (or any Portlet) would be launched within Jetspeed. - It would have XML like: <threading:parent>http://c.moreover.com/click/here.pl?r7597171a</threading:parent> Now withing PSML (or whatever) we can have our own threading that points to JCM. The JCM would produce RSS which would be a discussion based on it's parent :). At this point we have Jetspeed building content based on RSS and then re-syndicating it out via OCS. This is a good place to be :) 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]
