[Seaside] Re: Navigating away from call:'s

[Ronaldo Ferraz]

Hi, Boris--

Exactly. I was worried that I was doing something wrong replacing the
component and forgetting about it, but after reading more of the
SqueakSource and thinking about the way the back button works, it's
now clear that there's not problem in doing exactly that. Besides the
fact the Seaside components are very lightweight.

After reading Lukas answers, I've also reestructured parts of my
application to handle nesting more gracefully. Lots of learning in the
process, of course. :-)

Cheers,

Ronaldo

On Fri, Feb 22, 2008 at 1:40 AM, Boris Popov <boris at deepcovelabs.com> wrote:
> That kind of navigation is not uncommon. Imagine making a flight
> reservation, reviewing the checkout page and clicking on header navigation
> to get back to the home page. I would hate to be limited to next and
> previous buttons in that situation. If your component never answers, so be
> it. But you can always hit back in your browser and proceed and that's the
> whole point IMHO.