On Mon, July 25, 2005 3:38 pm, Michael Jouravlev said:
> Oh gosh, Frank, can you think more abstractively (is this a proper
> adjective?) It does not really matter, why login page follows welcome
> page, this is merely an *example*. Ok, consider that welcome page *is*
> a login page, but a user came from another site and after unsuccessful
> login attempt wants to return back to the previous site. Better?

Abstractly is the correct term, but that's not important :)

I don't care if the user can get to their previous site with one back
click from my site.  Not my problem.  How they navigate MY site is all I'm
paid to care about.

> Why??? They want to return from "login page" to whatever "previous
> page". I see only two pages here, why should they hit back 6 times???

You know, we've really gotten away from what was originally being
discussed here... we were talking about DispatchActions, and now we're
talking about redirect-after-post.  How did that happen?

> They expect a webapp, which navigates from page one to page two.
> Therefore, it should be possible to navigate from page two to page one
> in one click. Is not this logical? *That* is the way it should work.
> Instead, users have to deal with raw implementation of HTTP POST. They
> don't care about HTTP, they just want to go back from page two to page
> one.

I agree, but my point is that you are achieving this by defeating the
fundamental nature of the browser, whether that fundamental nature is good
or bad (and I would tend to agree with you that it is bad).  People tend
to perceive things that don't work as expected as being broken, even if
what they expected wasn't good to begin with.

> Actually, vintage browsers work great. It is the Opera which is a
> black sheep. Umm... should HD television be broadcasted? It is used by
> what? 1%, 3% of subscribers. Those who do not use it, get the same
> show with lower quality, that is it.
>
> Conversely to HD TV, Opera is used by only about 2% of users, and most
> of them use Opera specifically because it caches every page. These
> users like exactly this behavior and *they* expect that. So it is OK
> for them if they had to click Back six times.

Unless there is an alternative that solves the problem for all, and there
is, as I described earlier.  I'm not saying it's a BETTER solution,
because it has shortcomings too, but in this one regard I think it might
be better.

> Normal... hm... users expect just to return from page two to page one.
> If they use browser other than Opera, they get exactly what should
> happen, return from page two to page one. If they use the application
> on Opera, they have to click back six times, just like in most other
> applications, but application does not break because of this. Hell,
> fill it up with 89 instead of Sunoco 94, it will still be driveable,
> not that fast though :)

Until it starts knocking and makes my car seem to be broken. :)


But, I'd still like to know how we got to here from a discussion of
DispatchActions? :)

Frank

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

Reply via email to