<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Florent Guillaume wrote:
<blockquote cite="mid20050519140427.GA6305@bertha.in.nuxeo.com"
type="cite">
<pre wrap="">David H <a class="moz-txt-link-rfc2396E"
href="mailto:bluepaul@earthlink.net"><bluepaul@earthlink.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">If I might disagree, keeping a stable URL is not, by itself,
"user-defeating". For example, user's do not like browser history
clutter with subfolders and objects - all from the same application.
</pre>
</blockquote>
<pre wrap=""><!----></pre>
</blockquote>
<a class="moz-txt-link-abbreviated"
href="http://www.myApp.com/updateChartOfAccounts">www.myApp.com/updateChartOfAccounts</a>.
Because that would be "out of <br>
<blockquote cite="mid20050519140427.GA6305@bertha.in.nuxeo.com"
type="cite">
<blockquote type="cite">
<pre wrap="">context". Sure you can respond with an error message. But why should
they see it in the first place?
</pre>
</blockquote>
<pre wrap=""><!---->
They shouldn't, the application should be written in such a way that
this is a POST, and it won't appear in the history.
</pre>
</blockquote>
POST conceals parameters not paths from history. And I only described a
WAY to handle the problem.<br>
<blockquote cite="mid20050519140427.GA6305@bertha.in.nuxeo.com"
type="cite">
<pre wrap=""> </pre>
<blockquote type="cite">
<pre wrap="">With a stable URL they just click <a
class="moz-txt-link-abbreviated" href="http://www.myApp.com">www.myApp.com</a> and they get the main
page - every time.
</pre>
</blockquote>
<pre wrap=""><!---->
That's what bookmarks are for. You're trying to force your ideas of
bookmarking and history management to the users.
</pre>
</blockquote>
I wish I could impose my ideas on users. I respond to specs. Yes, I
will fight the good fight when a spec is silly. I've even turned down
gigs because the client was stubborn and what they wanted would be a
disaster. But URL "cloaking" is not silly to some clients and the
pattern I described handles it nicely and has benefits well beyond
maintaining a stable URL.<br>
Note: Sometimes I sense a "culture clash" between Advanced Zope
developement guys, Web presentation guys and us lowly application
developers that get the joy of accounting systems online.<br>
<blockquote cite="mid20050519140427.GA6305@bertha.in.nuxeo.com"
type="cite">
<pre wrap=""> </pre>
<blockquote type="cite">
<pre wrap="">The question remains - is there an elegant solution to this.
</pre>
</blockquote>
<pre wrap=""><!---->
What you call "stable URL" everybody else calls "cloaking" or "jailing".
It *is* hostile to the user.
</pre>
</blockquote>
Im curious, how is it "hostile" to a user? <br>
<br>
If
there are superior patterns (for Business Apps) Im the first that wants
to see them and this is a welcome discussion.<span
class="moz-smiley-s1"><span> :-) </span></span><br>
<br>
Thanks very much Florent,<br>
<br>
David<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>