I am going to remove the PortletConfig.getRunData().  All portlets
should work fine without the RunData.  The only one that won't is Cocoon
but I am going to hard code a specific exception for this Portlet. 
(with the words "BEGIN KLUDGE HERE" stamped all over it).

This should allow somewhat headless operation of Jetspeed.  So that
means that the FeedDaemon is going to (optional feature) instantiate all
portlets as part of it's operation.  This way after Jetspeed is
initialized performance will be very good.

I am going to also add a *very* basic in-memory search feature so that
we can run queries (with the PortletBrowser) across Portlets.  Since we
currently have like 1700 RSS channels this is kind of important.  After
the FeedDaemon instantiates the Portlets it will put it into the
in-memory object search engine 

This will help out a *lot* with customization.  Users can logon and then
be sent to the PortletBrowser which will allow them to browse or search
for content and then subscribe to it.

I also tried to hack in Mozilla support.  But it looks like there are
still massive bugs here.  I am starting to get very disappointed in the
whole mozilla project.  3 years later and they still have junk!  Must be
nice to be a Netscape Engineer and get paid for 3 years and you don't
have to deliver a product :)

Kevin

-- 
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN:  "Please Open Source Java!"
The house of the unbelievers shall be razed and they shall be
scorched to the earth. Their code will be open until the end of days.


--
--------------------------------------------------------------
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]

Reply via email to