Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v612)
In-Reply-To: <20040310012958.95999.qmail@web61108.mail.yahoo.com>
References: <20040310012958.95999.qmail@web61108.mail.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <9660AE30-7348-11D8-BD77-000A95DB830C@misgl.com>
Content-Transfer-Encoding: quoted-printable
From: Jon Evans <jon.evans@misgl.com>
Subject: Re: coplet / flowscript cache invalidation question
Date: Thu, 11 Mar 2004 10:41:00 +0000
To: <users@cocoon.apache.org>

Hi Alex,

On 10 Mar 2004, at 01:29, Alex Romayev wrote:

> Maybe I'm missing something, but why can't you just
>  set the state of your coplet in the flowscript, so
>  that it shows the first page after it's done?
>
> e.g.:
>
> if (state =3D=3D 'done')
>  =A0cocooon.sendPage(welome-page);
>

Thanks for your reply.

The thing is, in my flowscript I can keep track of the state, but once=20=

the CachingURICoplet has displayed my final page it doesn't call the=20
flowscript again because the page always comes from the cache.

So I need a programmatic way of saying:

state =3D start_again_at_page_one;
cocoon.thisCoplet().dontCacheTheFollowingPage();
cocoon.sendPage(final-page);

Alternatively, I need a way to hook into the event that says "user=20
switched back to this tab on the layout" and send an event to this=20
particular coplet to get it to invalidate its cache.

In fact, for future reference it would be useful to know something=20
about hooking into, and sending, portal events.  Don't suppose you=20
could give me some pointers?

Many thanks,

Jon=


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org