Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <20040503145325.589.qmail@web90103.mail.scd.yahoo.com>
Date: Mon, 3 May 2004 07:53:25 -0700 (PDT)
From: Alex Romayev <romayev@yahoo.com>
Subject: RE: [portal] Transfering control from CachingURICoplet to portal
To: dev@cocoon.apache.org
In-Reply-To: <OF50000FDB.156504FE-ONC1256E89.004F4212@sundn.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Carsten Ziegeler <cziegeler@s-und-n.de> wrote:
> Alex Romayev wrote:
> > 
> > Carsten, is there another way of doing this, say
> directly 
> > from flow?  I really don't see this as a one-off
> case, where 
> > a client JavaScript workaround is good enough.
> > 
> Hmm, I think not - you have to do a global redirect
> there and
> this is imho not possible with the portal.
> 
> Carsten
> 

Seems like a fairly common use case though,
registration is one example.  A couple of others:

- "Edit saved search": on submit, write the edited
search to the database, open another page which would
run the search and display the results.
- "Edit user preferences", on submit save info to the
database and open a portal page reflecting the new
preferences.

Is there another way of implementing these types of
coplets, other than CachingURICoplet, which work
better within portal?

-Alex