Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: John M <howdymatey@ho...> - 2004-08-18 06:25:45
<html><div style='background-color:'><DIV class=RTE>
<P>Had a late night last night so I may be wrong here but here is my idea.</P>
<P>Thierry, since your customers dont really use any of the dynamic features of rainbow (apart from <BR>Html module for editing) why dont you cache DesktopDefault and vary it by param (Querystrings such as tabid, lang etc)? You can set it for 20 mins or what ever takes your fancy.</P>
<P>What about adding content moving modules etc I here you ask?</P>
<P>Well Create a Copy of DesktopDefault.aspx Called DesktopAdmin for example. It is basically a copy of DesktopDefault.aspx (Still pointing at DestopDefault.aspx.cs) but it doesn't have caching set on the aspx page. That way you will see the uncached version and can use that for editing. Then all you need to do is create a quick module called invalidate cache. Do all you editing via DesktopAdmin.aspx (From what you said this will not be often) and then click the invalidate cache button to refresh DesktopDefault.aspx.</P>
<P>Now this may not be a great thing for all situations but for your one it should do fine.</P>
<DIV></DIV>>From: "Thierry (Tiptopweb)" <thierry@...>
<DIV></DIV>>Subject: [Rainbowportal-devel] caching pages on disk ?
<DIV></DIV>>Date: Tue, 17 Aug 2004 05:02:55 +0200
<DIV></DIV>>As I am selling Rainbow sites to my customers. Most of the time turning an
<DIV></DIV>>html site into a Rainbow site, I have to handle the problem of speed.
<DIV></DIV>>Sometimes, customers will like the content management, but not be really
<DIV></DIV>>interested in the personalisation of the content.
<DIV></DIV>>Sometimes they would most of the time use the HTML module and this is it.
<DIV></DIV>>This is a process to have clients use all the features of Rainbow, they will
<DIV></DIV>>simply not in the beginning.
<DIV></DIV>>In that case, the speed is an issue, Rainbow is too slow from their
<DIV></DIV>>viewpoint and for how they are using it.
<DIV></DIV>>At this point, do not take me wrong: I want to acknowledge all the work that
<DIV></DIV>>has been done to improve the speed of Rainbow and Esperantus by Manu and
<DIV></DIV>>SO my idea is the following:
<DIV></DIV>>- what about having a button on the pages. On demand and if the page is
<DIV></DIV>>appropriate, the admin would be able to save the generated content of the
<DIV></DIV>>page as (for example) <GUID>.aspx and indicate this to the URL handler
<DIV></DIV>>(maybe an xml file).
<DIV></DIV>>This would be like caching these pages on the server and would speed up them
<DIV></DIV>>definitely for these types of clients.
<DIV></DIV>>Other pages will be delivered in the normal way.
<DIV></DIV>>My questions are now: what do people think of this idea?
<DIV></DIV>>Can someone think of something more elegant or outside my frame of thoughts?
<DIV></DIV>>And the inevitable question: someone wants to help with this???
<DIV></DIV></div><br clear=all><hr>MSN Premium gives you PC protection, junk-mail filters, advanced communication tools and great software like MSN Encarta® Premium. <a href="http://g.msn.com/8HMAENUK/2749??PS=47575">Click here for a FREE trial!</a> </html>