Ed Knutson wrote:
>
> Disregard the previous message. For some reason, it did not occur to me
> that Tomcat places servlets in the /servlet path of the context for which
> they are defined. Now, everything works ok, so far (although I thought
> somebody said a while ago that the PortletBrowser was working).
It is... are you having problems?
> For the
> next few days, I actually get to program for once, so I'll be working on the
> cache and portlet browsing/selection features.
Cool. What features of the cache? Memory cache? Disk cache?
One of the things that needs to be worked on in the browsing/selection
arena is to have per-user portlet subscription with persistence. I
haven't worked on this because it isn't a big issue in my current
situation. It is important though.
>
> Question: wouldn't it be a lot easier on the server if we could store *some*
> of the config info in cookies? This is a big issue for me, because my
> company is already maxed out on db space and server cycles....
Not really. The only real issue I think should be stored as cookies is
the username/password (only if password is allowed) so that the user can
autologon. Writing a cookie store for your portlets would be a bad
idea. Specifically because you don't leverage a clean server-side impl.
Honestly I would just throw a little more resources into it. If you
have a suggestion I am always open though.
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
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]
