----- Original Message -----
From: "Kevin A. Burton" <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Wednesday, March 22, 2000 6:02 PM
Subject: Re: congrats, but....
> > 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?
It isn't displaying any portlets. The test site url is
http://maia.webcombo.net:8080/content/servlet/jetspeed
When I go to the Channels link, it first chops the domain
name off the
server (this may be something I have misconfigured). But
even if you put
the .webcombo.net back on, an empty Jetspeed screen comes
up with a portlet
labelled Portlets and a Next button----but no portlet list.
> > 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?
Disk cache first. Right now, our home page at
www.webcombo.net is generated
into a static page using lynx -source w/ 1.0b2. We have 3
different
versions on two servers updated 4 times per hour. This
means that each
portlet gets accessed by our server 24 times per hour. My
first goal is to
get the disk cache to the point where it only loads the url
if it has
changed since the last hit. Memory cache is a low priority
for me, because
all of our servers have great big raid arrays but very (for
production
servers) small memory.
> 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.
This is my top priority after the cache.
> > 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.
I dislike the idea of storing passwords in cookies, because
they get stored
as plain text on the computer. Plus, what if somebody puts
up Jetspeed on a
doubleclick-esque site? Wouldn't want a third party
building a database of
passwords....
The idea of using cookies was brought up by my sys admin
specifically
because our MySQL server is running on his workstation and
already has way
too much load. I think we will start with cookies storing
very basic
settings and migrate towards a complete db impl once we get
a little more
hardware.
We have had our basic system live for two weeks and have
received a lot of
positive feedback. Oh, that reminds me, I'm also going to
work on the XML
subscription thing. We use moreover feeds formatted by
cocoon and merged
with the jetspeed document through an icky hack. I'd like
to get it to the
point where it can all be xml. I favor cocoon generating
verbose html vs.
CSS because a lot of our users don't support CSS
(consistently).
So----I am basing all of this off of the todo I found in the
/jetspeed/dist/Jetspeed-1.0.zip. Is there a more recent
version attached to
a more specific module?
-ed
---------------------------------------------------
webCOMBO - Americas's Free Internet Access Provider
http://www.webcombo.net
--
--------------------------------------------------------------
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]
