Chris,

Jetspeed uses files in the <jetspeed-home>/WEB-INF/templates/...
directory to generate a page.  So you should be able to convert from
nested frames to frames/iframes by editing those files.  I have seen
some traffic on this list about using frames/iframes, but no one has
contributed files that support frames/iframes.

By the way, some sites use nested frames go encourage customer to use IE :(

Paul Spencer

Christoph Steinbeck wrote:

 > Paul,
 >
 > thanks for the quick answer. And you solved the mystery. The problem is
 > Netscape 4.7x. D**n!
 > Internet Explorer and Mozilla show the pages instantaneously.
 > The effect is dramatic. 15 sec for showing the entry sceen on Netscape
 > 4.78.. The logo and everything above the thin line (login form, etc.)
 > was there immediately but the rest of the portlets (jetspeed, apache
 > jetspeed, welcome) takes those 15 sec to appear.
 >
 > I don't want any "This page is worst viewed with NS 4.7x" logos on my
 > site. :-)
 >
 > Cheers,
 >
 > Chris
 >
 > --
 > Dr. Christoph Steinbeck (http://www.ice.mpg.de/departments/ChemInf)
 > MPI of Chemical Ecology, Winzerlaer Str. 10, Beutenberg Campus, 07745
 > Jena, Germany
 > Tel: +49(0)3641 571263 - Fax: +49(0)3641 571202
 >
 > What is man but that lofty spirit - that sense of enterprise.
 > ... Kirk, "I, Mudd," stardate 4513.3..
 >
 >
 >
 >
 >
 > Paul Spencer wrote:
 >
 >>Chris,
 >>As you pointed out, performance is based in many factors.  The retrieval
 >>portlet content is one.  Another is related to how fast the browser can
 >>render the returned page.  Netscape 4.7x has a known performance problem
 >>with nested tables.  Jetspeed uses nested tables :(
 >>
 >>10 second is a long time to display the Jetspeed home page.  I am not
 >>seeing this.  Most of the time Jetspeed's home page is displayed in <1
 >>second.  By the way, thank you for quantifying "slow performance" !!
 >>
 >>Places to look:
 >>o Log files!  Including Jetspeed's, Tomcat's, and the web server's.
 >>o General performance on the server machine(s), i.e. if server is
 >>   low on memory it will spend a lot of time swapping pages instead
 >>   of running applications.
 >>o Load and configuration on the client machine, i.e. is the client
 >>   a 100 MHz PII with 16 MB of memory?
 >>o Proxies, the lurk on corporate networks and can cause caching and
 >>   performance problems :(
 >>o Firewalls can prevent prevent content retrieval and cause jetspeed
 >>   to wait for the request to time-out.
 >>o General network performance
 >>
 >>Paul Spencer
 >>
 >>Christoph Steinbeck wrote:
 >>
 >>
 >>>Hi everybody,
 >>>
 >>>I must say that this latest release of Jetspeed-1.3a2 is a great
 >>>achievement. I was able to run and configure it (including email
 >>>confirmation, etc.) within a few minutes.
 >>>Now, since we are planning to use this for a scientific database
 >>>front-end, I was wondering whether the relatively slow response times
 >>>that I get here, are
 >>>
 >>>- due to a problem on my side, or
 >>>- a known problem, or
 >>>- a feature, not a bug :-)
 >>>
 >>>and whether one can do anything about it.
 >>>
 >>>I understand that if you have all these news feed portlets switched on,
 >>>the response can be slowed down due to non reachable sites somewhere
 >>>else.
 >>>Indeed, when I switched off all these feed-portlets, I could reduce the
 >>>time for a page to appear from several minutes to less then ten seconds.
 >>>But of course, that's still too slow. Are there some caching features,
 >>>that need to switched on, or anything else I can do about it?
 >>>
 >>>Cheers,
 >>>
 >>>Chris
 >>>
 >>>--
 >>>Dr. Christoph Steinbeck (http://www.ice.mpg.de/departments/ChemInf)
 >>>MPI of Chemical Ecology, Winzerlaer Str. 10, Beutenberg Campus, 07745
 >>>Jena, Germany
 >>>Tel: +49(0)3641 571263 - Fax: +49(0)3641 571202
 >>>
 >>>What is man but that lofty spirit - that sense of enterprise.
 >>>... Kirk, "I, Mudd," stardate 4513.3..
 >>>
 >>>--
 >>>To unsubscribe, e-mail: 
<mailto:[EMAIL PROTECTED]>
 >>>For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>
 >>>
 >>>
 >>--
 >>To unsubscribe, e-mail: 
<mailto:[EMAIL PROTECTED]>
 >>For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>
 >>
 >
 > --
 > To unsubscribe, e-mail: 
<mailto:[EMAIL PROTECTED]>
 > For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>
 >
 >




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to